Re: pg_basebackup failure after setting default_table_access_methodoption

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: pg_basebackup failure after setting default_table_access_methodoption
Дата
Msg-id 20190611064903.ipuawi3dmz2wkdo4@alap3.anarazel.de
обсуждение исходный текст
Ответ на Re: pg_basebackup failure after setting default_table_access_methodoption  (Michael Paquier <michael@paquier.xyz>)
Ответы Re: pg_basebackup failure after setting default_table_access_methodoption  (Michael Paquier <michael@paquier.xyz>)
Список 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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Fabien COELHO
Дата:
Сообщение: Re: pgbench rate limiting changes transaction latency computation
Следующее
От: Amit Khandekar
Дата:
Сообщение: Re: Minimal logical decoding on standbys