Re: pgsql: Add more $Test::Builder::Level in the TAP tests

On Fri, Oct 15, 2021 at 11:22 PM Michael Paquier wrote: > Hearing nothing, I have just poked at this problem. > Peter, does it take care of your problem? Yes, it does. Thank you for taking care of this. -- Peter Geoghegan

pgsql: Avoid core dump in pg_dump when dumping from pre-8.3 server.

Avoid core dump in pg_dump when dumping from pre-8.3 server. Commit f0e21f2f6 missed adding a tgisinternal output column to getTriggers' query for pre-8.3 servers. Back-patch to v11, like that commit. Branch -- REL_13_STABLE Details --- https://git.postgresql.org/pg/commitdiff/0b5f557b7

pgsql: Avoid core dump in pg_dump when dumping from pre-8.3 server.

Avoid core dump in pg_dump when dumping from pre-8.3 server. Commit f0e21f2f6 missed adding a tgisinternal output column to getTriggers' query for pre-8.3 servers. Back-patch to v11, like that commit. Branch -- REL_12_STABLE Details --- https://git.postgresql.org/pg/commitdiff/5b0b2983a

pgsql: Avoid core dump in pg_dump when dumping from pre-8.3 server.

Avoid core dump in pg_dump when dumping from pre-8.3 server. Commit f0e21f2f6 missed adding a tgisinternal output column to getTriggers' query for pre-8.3 servers. Back-patch to v11, like that commit. Branch -- REL_14_STABLE Details --- https://git.postgresql.org/pg/commitdiff/3e4c8db93

pgsql: Avoid core dump in pg_dump when dumping from pre-8.3 server.

Avoid core dump in pg_dump when dumping from pre-8.3 server. Commit f0e21f2f6 missed adding a tgisinternal output column to getTriggers' query for pre-8.3 servers. Back-patch to v11, like that commit. Branch -- REL_11_STABLE Details --- https://git.postgresql.org/pg/commitdiff/58955c84f

pgsql: Avoid core dump in pg_dump when dumping from pre-8.3 server.

Avoid core dump in pg_dump when dumping from pre-8.3 server. Commit f0e21f2f6 missed adding a tgisinternal output column to getTriggers' query for pre-8.3 servers. Back-patch to v11, like that commit. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/40dfac4fc4776213

pgsql: Make pg_dump acquire lock on partitioned tables that are to be d

Make pg_dump acquire lock on partitioned tables that are to be dumped. It was clearly the intent to do so all along, but the original coding fat-fingered this by checking the wrong array element. We fixed it in passing in 403a3d91c, but that later got reverted, and we forgot to keep this bug fix.

pgsql: Make pg_dump acquire lock on partitioned tables that are to be d

Make pg_dump acquire lock on partitioned tables that are to be dumped. It was clearly the intent to do so all along, but the original coding fat-fingered this by checking the wrong array element. We fixed it in passing in 403a3d91c, but that later got reverted, and we forgot to keep this bug fix.

pgsql: Make pg_dump acquire lock on partitioned tables that are to be d

Make pg_dump acquire lock on partitioned tables that are to be dumped. It was clearly the intent to do so all along, but the original coding fat-fingered this by checking the wrong array element. We fixed it in passing in 403a3d91c, but that later got reverted, and we forgot to keep this bug fix.

pgsql: Make pg_dump acquire lock on partitioned tables that are to be d

Make pg_dump acquire lock on partitioned tables that are to be dumped. It was clearly the intent to do so all along, but the original coding fat-fingered this by checking the wrong array element. We fixed it in passing in 403a3d91c, but that later got reverted, and we forgot to keep this bug fix.

pgsql: Make pg_dump acquire lock on partitioned tables that are to be d

Make pg_dump acquire lock on partitioned tables that are to be dumped. It was clearly the intent to do so all along, but the original coding fat-fingered this by checking the wrong array element. We fixed it in passing in 403a3d91c, but that later got reverted, and we forgot to keep this bug fix.

pgsql: Make pg_dump acquire lock on partitioned tables that are to be d

Make pg_dump acquire lock on partitioned tables that are to be dumped. It was clearly the intent to do so all along, but the original coding fat-fingered this by checking the wrong array element. We fixed it in passing in 403a3d91c, but that later got reverted, and we forgot to keep this bug fix.