I wrote:
> Christophe Pettus writes:
>> A bit more poking revealed the reason: The ON HOLD cursor's query is
>> executed at commit time (which is, logically, not interruptible), but that's
>> all wrapped in the single statement outside of a transaction.
> Hmm ... seems like a bit of a UX failur
Thanks. I was sort of expecting that answer but I didn't see where it
was addressed specifically. Unfortunately I'm stuck on v12 for the
time being so I guess it's back to the workaround.
On Tue, Sep 28, 2021 at 2:13 PM Tom Lane wrote:
>
> Jeff Hoffmann writes:
> > I am using postgresql-12.8.
Jeff Hoffmann writes:
> I am using postgresql-12.8. I am using I am making use of an identity
> column for part of a scripts to process some updated data. Because of
> the way the script is called I don't necessarily know if this column
> is going to exist in the table I am working on so I have
I am using postgresql-12.8. I am using I am making use of an identity
column for part of a scripts to process some updated data. Because of
the way the script is called I don't necessarily know if this column
is going to exist in the table I am working on so I have a step that
will conditionally
On Tue, Sep 28, 2021 at 9:36 AM Tom Lane wrote:
> I don't think it's possible to do it without huge ambiguity
> problems, unless you introduce some separator other than dot, as indeed
> you suggest here.
Heh... the moment I saw you'd replied, I thought, "Uh oh!"... because
I think of you as "the
On Tue, Sep 28, 2021 at 10:13 AM rob stone wrote:
> Double colons are used for casting.
> E.g., $1::INET or $1::INTEGER where $1 is a string.
Quite right; slipped my mind. Thank you.
--
Ray Brinzer
Hello Ray,
On Tue, 2021-09-28 at 09:24 -0400, Raymond Brinzer wrote:
> Greetings.
>
>
>
> I'm wondering whether such a feature could be added, without breaking
> either existing code, or compliance with the SQL standard. For
> instance, borrowing :: from languages like Ruby and Perl:
>
> SELE
Raymond Brinzer writes:
> So, for example, I'd like to be able to say something like this:
> SELECT * FROM /projects/contacts/people;
I looked into this many years ago. (The reason why pg_namespace is called
that and not pg_schema is exactly that I thought it might someday include
sub-schemas.)
Greetings.
For some people the "what?" and "why?" of this will be immediately
obvious from the title, but I'm going to spend a little time on those
before "whether?" and "how?"
We have schemata. They're namespaces; very convenient for organizing
things. They let you group tables and other entit
