Re: pg_dump bug for extension owned tables
Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
From: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
To: fabriziomello@gmail.com
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-07-11T23:07:07Z
Lists: pgsql-hackers
On 6/26/20 2:10 PM, Fabrízio de Royes Mello wrote: > > On Fri, Jun 26, 2020 at 11:55 AM Fabrízio de Royes Mello > <fabriziomello@gmail.com <mailto:fabriziomello@gmail.com>> wrote: > > > > > > On Fri, Jun 26, 2020 at 11:24 AM Andrew Dunstan > <andrew.dunstan@2ndquadrant.com > <mailto:andrew.dunstan@2ndquadrant.com>> wrote: > > > > > > > > > On 6/26/20 9:57 AM, Andrew Dunstan wrote: > > > > It appears that for extension owned tables tbinfo.attgenerated isn't > > > > being properly populated, so line 2050 in REL_12_STABLE, which > is line > > > > 2109 in git tip, is failing. > > > > > > > > > > > > > > Should have mentioned this is in src/bin/pg_dump/pg_dump.c > > > > > > > Having a look on it. > > > > Seems when qualify the schemaname the the "tbinfo->interesting" field > is not setted for extensions objects, so the getTableAttrs can't fill > the attgenerated field properly. > > I'm not 100% sure it's the correct way but the attached patch works > for me and all tests passed. Maybe we should add more TAP tests? > > I just tried this patch out on master, with the test case I gave upthread. It's not working, still getting a segfault. Will look closer. cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Rethink recent fix for pg_dump's handling of extension config tables.
- 710c0a66d6e9 9.6.20 landed
- 0bfe356c5594 9.5.24 landed
- f2c6e94f0790 11.10 landed
- 0c79dcb36c52 10.15 landed
- d8c2a2199867 12.5 landed
- 2ea624b4b51c 13.1 landed
- 9e5f1f21ad6a 14.0 landed