Re: pg_basebackup failure after setting default_table_access_method option
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Michael Paquier <michael@paquier.xyz>
Cc: Haribabu Kommi <kommi.haribabu@gmail.com>, vignesh C <vignesh21@gmail.com>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2019-06-11T06:49:03Z
Lists: pgsql-hackers
Hi, On 2019-06-11 14:56:36 +0900, Michael Paquier wrote: > On Mon, Jun 10, 2019 at 10:33:37PM -0700, Andres Freund wrote: > > Yea, that's where the default_table_access_method code originates from, > > obviously. I'll backpatch the default_text_search_config fix separately > > (and first). > > So you are just planning to add a check on MyDatabaseId for both? No > objections to that. Well, all four. Given it's just copied code I don't see much code in splitting the commit anymore. I noticed some other uglyness: check_timezone calls interval_in(), without any checks. Not a huge fan of doing all that in postmaster, even leaving the wrong error reporting aside :(. But that seems like a plenty different enough issue to fix it separately, if we decide we want to do so. Greetings, Andres Freund
Commits
-
Don't access catalogs to validate GUCs when not connected to a DB.
- 69f32206d7e5 9.4.23 landed
- 483b2d7ae173 9.5.18 landed
- b8607e15e0fa 9.6.14 landed
- 52ad5fc0a6c3 10.9 landed
- c0155601763a 11.4 landed
- fff2a7d7bd09 12.0 landed