Re: pg_dump assertion failure with "-n pg_catalog"
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Jeff Davis <pgsql@j-davis.com>
Cc: pgsql-bugs@postgresql.org
Date: 2023-06-16T05:29:41Z
Lists: pgsql-bugs
On Thu, Jun 15, 2023 at 03:47:59PM -0700, Jeff Davis wrote: > The new patch does add about 40 net lines, though. I have looked at dumps generated from servers down to 9.2, and these seemed OK. > Given that it fixes an obscure issue, I'm not even sure if it should be > backported -- perhaps it could just go in 17 as more of a cleanup than > a bugfix? Not sure to agree about this point. The first version where this happens is v15, meaning that two branches are impacted currently. So the cost of backpatch is minimal. > Even aside from the issue fixed by this patch, there are other warnings > emitted when dumping pg_catalog related to types with typtype='p' and > typisdefined=t. Right, there are 14 of them, except _record. This is actually much, much older than the collation bits. -- Michael
Commits
-
Fix pg_dump assertion failure when dumping pg_catalog.
- 37188cea0c16 17.0 landed
- 501704e826fc 16.0 landed
- 1d9976d1bd00 15.5 landed