Re: pg_dump bug for extension owned tables
Fabrízio de Royes Mello <fabriziomello@gmail.com>
From: Fabrízio de Royes Mello <fabriziomello@gmail.com>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-07-13T21:18:37Z
Lists: pgsql-hackers
On Mon, Jul 13, 2020 at 5:05 PM Andrew Dunstan < andrew.dunstan@2ndquadrant.com> wrote: > > > On 7/13/20 2:46 PM, Fabrízio de Royes Mello wrote: > > > > > > > > > > yeah, that's the fix I came up with too. The only thing I added was > > > "Assert(tbinfo->attgenerated);" at about line 2097. > > > > > > > Cool. > > > > > > > > Will wait for your TAP tests. > > > > > > > Actually I've sent it already but it seems to have gone to the > > moderation queue. > > > > Anyway attached with your assertion and TAP tests. > > > > > > > > Thanks, that all seems fine. The TAP test changes are a bit of a pain in > the neck before release 11, so I think I'll just do those back that far, > but the main fix for all live branches. > Sounds good to me. -- Fabrízio de Royes Mello Timbira - http://www.timbira.com.br/ PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
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