Correct error message for row-level triggers with transition tables on
partitioned tables.
"Triggers on partitioned tables cannot have transition tables." is
incorrect as we allow statement-level triggers on partitioned tables to
have transition tables.
This has been wrong since commit 86f575948
Correct error message for row-level triggers with transition tables on
partitioned tables.
"Triggers on partitioned tables cannot have transition tables." is
incorrect as we allow statement-level triggers on partitioned tables to
have transition tables.
This has been wrong since commit 86f575948
Correct error message for row-level triggers with transition tables on
partitioned tables.
"Triggers on partitioned tables cannot have transition tables." is
incorrect as we allow statement-level triggers on partitioned tables to
have transition tables.
This has been wrong since commit 86f575948
Correct error message for row-level triggers with transition tables on
partitioned tables.
"Triggers on partitioned tables cannot have transition tables." is
incorrect as we allow statement-level triggers on partitioned tables to
have transition tables.
This has been wrong since commit 86f575948
Correct error message for row-level triggers with transition tables on
partitioned tables.
"Triggers on partitioned tables cannot have transition tables." is
incorrect as we allow statement-level triggers on partitioned tables to
have transition tables.
This has been wrong since commit 86f575948
Correct error message for row-level triggers with transition tables on
partitioned tables.
"Triggers on partitioned tables cannot have transition tables." is
incorrect as we allow statement-level triggers on partitioned tables to
have transition tables.
This has been wrong since commit 86f575948
Fix CREATE DATABASE so we can pg_upgrade DBs with OIDs above 2^31.
Commit aa0105141 repeated one of the oldest mistakes in our book:
thinking that OID is the same as int32. It isn't of course, and
unsurprisingly the first person who came along with a database
OID above 2 billion broke it. Repair
Fix CREATE DATABASE so we can pg_upgrade DBs with OIDs above 2^31.
Commit aa0105141 repeated one of the oldest mistakes in our book:
thinking that OID is the same as int32. It isn't of course, and
unsurprisingly the first person who came along with a database
OID above 2 billion broke it. Repair
On Thu, Nov 03, 2022 at 03:41:56PM +, Alvaro Herrera wrote:
> Resolve partition strategy during early parsing
>
> This has little practical value, but there's no reason to let the
> partition strategy names travel through DDL as strings.
>
> Reviewed-by: Japin Li
> Discussion: https://postgr
First-draft release notes for 15.1.
As usual, the release notes for other branches will be made by cutting
these down, but put them up for community review first.
Also as usual for a .1 release, there are some entries here that
are not really relevant for v15 because they already appeared in 15.0
meson: Split 'main' suite into 'regress' and 'isolation'
Several people didn't like the 'main' name and found it confusing that the
main regression and isolation tests were in one suite.
Author: Justin Pryzby
Discussion:
https://postgr.es/m/20221001221514.2yy257v4zdfhw...@awork3.anarazel.de
Dis
meson: Mark PROVE as not required
In the meson build the prove binary is currently not even used. It will soon
be, for PGXS compatibility, but even then we should build without it around.
Author: Justin Pryzby
Discussion: https://postgr.es/m/20221021034040.gt16...@telsasoft.com
Discussion: https
Remove unneeded includes of
Since bfb9dfd, none of the files updated in this commit have any stat()
calls, so these inclusions are not necessary, for the same reasons as
233cf6e.
Per discussion with John Naylor.
Discussion:
https://postgr.es/m/cafbsxsgggx7kd6rxbnosjzusc8gz3hoxcfhtomlb_hjcm68..
13 matches
Mail list logo
