The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/13/ddl-partitioning.html
Description:
I would like to add a sentence like this into the description of
partitions:
You receive the name of the partition table data is from using
Thanks! Perhaps this behavior should also be explained elsewhere. It didn't
occur to me to look in the "Compatibility" section.
On Wed, Jul 14, 2021 at 3:33 AM Pantelis Theodosiou
wrote:
> UNIQUE constraints have this behaviour. It is explained in the section:
>
> Non-Deferred Uniqueness
UNIQUE constraints have this behaviour. It is explained in the section:
Non-Deferred Uniqueness Constraints
When a UNIQUE or PRIMARY KEY constraint is not deferrable, PostgreSQL checks
for uniqueness immediately whenever a row is inserted or modified. The SQL
standard says that uniqueness should
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/13/sql-createtable.html
Description:
According to the docs:
A constraint that is not deferrable will be checked immediately after every
command.
But this is the behavior I observe on PG
