Re: pg_basebackup failure after setting default_table_access_methodoption - Mailing list pgsql-hackers

From Andres Freund
Subject Re: pg_basebackup failure after setting default_table_access_methodoption
Date
Msg-id 20190611053337.klqzlsk65e32o3b7@alap3.anarazel.de
Whole thread Raw
In response to Re: pg_basebackup failure after setting default_table_access_methodoption  (Michael Paquier <michael@paquier.xyz>)
Responses Re: pg_basebackup failure after setting default_table_access_methodoption
List 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



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: pgbench rate limiting changes transaction latency computation
Next
From: Michael Paquier
Date:
Subject: Re: [pg_rewind] cp: cannot stat ‘pg_wal/RECOVERYHISTORY’ No suchfile or directory