Hi,
I was testing creating a rule that uses RETURNING and noticed a difference
between the extended query protocol and the simple query protocol. In the
former, RETURNING is ignored (at least in my case) and the latter it is
respected:
CREATE table test (id bigint, deleted boolean);
CREATE RULE
Hi,
I work on a driver for Postgres that utilizes the extended query protocol
and have a question about the row description message for interval types.
I am trying to use the type modifier value from the message to determine
the precision of the interval. This is something I can do for timestamp
Apr 1, 2021 at 2:32 AM Michael Paquier wrote:
> On Tue, Mar 30, 2021 at 11:29:17PM -0400, Greg Rychlewski wrote:
> > Thanks for pointing that out. I've attached a new patch with several
> other
> > updates where I felt confident the docs were referring to an ACCESS
> > E
Thanks for pointing that out. I've attached a new patch with several other
updates where I felt confident the docs were referring to an ACCESS
EXCLUSIVE lock.
On Tue, Mar 30, 2021 at 8:47 PM Michael Paquier wrote:
> On Tue, Mar 30, 2021 at 10:33:46AM -0400, Greg Rychlewski wrote:
&
Hi,
While reading the documentation for DROP INDEX[1], I noticed the lock was
described colloquially as an "exclusive" lock, which made me pause for a
second because it's the same name as the EXCLUSIVE table lock.
The attached patch explicitly states that an ACCESS EXCLUSIVE lock is
acquired.
[1
