Re: BUG #16655: pg_dump segfault when excluding postgis table
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephen Frost <sfrost@snowman.net>
Cc: cam.daniel@gmail.com, pgsql-bugs@lists.postgresql.org
Date: 2020-10-07T16:56:05Z
Lists: pgsql-bugs
Stephen Frost <sfrost@snowman.net> writes: > This all sounds like a reasonable approach to me. I've gone back and > looked through things a bit and agree that processExtensionTables really > should be setting interesting to true for extension config tables when > we decide we want to include them. Your 0003 patch looks correct to me, > and it does seem like we need to go all the way back with that. Pushed now, thanks for looking it over. I ended up dropping 0001 (the ncheck refactoring). That's not really relevant to the bug fix, and it occurred to me that dumping core if the checkexprs data isn't there isn't such a bad thing. 0001 would have led us to silently act as though the table has no CHECK constraints, contrary to reality, if we reached one of those loops without having loaded the requisite data. Crashing is better --- think of it as a free Assert ;-). regards, tom lane
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