Simon Norris writes:
> I noticed a very small problem in the intarray docs example.
> Trying out the example gives below error, the example uses the wrong
> parameter for the given operator class:
> db=# CREATE TABLE message (mid INT PRIMARY KEY, sections INT[]);
> CREATE TABLE
> db=# CREATE IND
Hey,
The example in the update documentation that does an upsert using a
savepoint seems like it should just go away now that we have insert...on
conflict. Making an explicit reference (and link) to that feature in the
Update documentation should be added in its place (well, under notes).
David
Hi list,
I noticed a very small problem in the intarray docs example.
Trying out the example gives below error, the example uses the wrong parameter
for the given operator class:
db=# CREATE TABLE message (mid INT PRIMARY KEY, sections INT[]);
CREATE TABLE
db=# CREATE INDEX message_rdtree_idx ON
> I don't follow why you put this documentation under ALTER TABLE ... DROP
> EXPRESSION. That action doesn't seem related to what you were hoping to do.
I thought that's where it would be if we had ADD/SET EXPRESSION
statements, just like the ADD/SET GENERATED statements just below.
Good catch.
Thanks, I will fix that.
Dave Cramer
www.postgres.rocks
On Thu, 3 Jun 2021 at 03:49, Celinio Fer wrote:
> Hi,
> I wonder if the documentation for the JDBC PostgreSQL driver is up to date
> :
> https://jdbc.postgresql.org/documentation/head/ds-cpds.html#ds-cpds-props
> It is written
Hi,
I wonder if the documentation for the JDBC PostgreSQL driver is up to date :
https://jdbc.postgresql.org/documentation/head/ds-cpds.html#ds-cpds-props
It is written that the default value for the defaultAutoCommit property is
false.
However in the source code, the default value is true :
ht
