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-11T05:33:37Z
Lists: pgsql-hackers
Hi, On 2019-06-10 16:37:33 +0900, Michael Paquier wrote: > On Sat, Jun 08, 2019 at 08:26:07AM -0700, Andres Freund wrote: > > We have plenty other callbacks that aren't bulletproof, so I don't think > > this is really something we should / can change in isolation here. > > Good point. I was looking at the check callbacks in guc.c for similar > changes, and missed these. After testing, only these parameters fail > with the same error: > - default_table_access_method > - default_text_search_config > > For the second one it's much older. 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). 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