Re: StandbyAcquireAccessExclusiveLock doesn't necessarily

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: StandbyAcquireAccessExclusiveLock doesn't necessarily
Дата
Msg-id 20180911152929.7xo4qgb3eyz6djfu@alap3.anarazel.de
обсуждение исходный текст
Ответ на Re: StandbyAcquireAccessExclusiveLock doesn't necessarily  (Simon Riggs <simon@2ndquadrant.com>)
Ответы Re: StandbyAcquireAccessExclusiveLock doesn't necessarily  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Hi,

On 2018-09-11 16:23:44 +0100, Simon Riggs wrote:
> It's hard to see how any reasonable workload would affect the standby. And
> if it did, you'd change the parameter and restart, just like you already
> have to do if someone changes max_connections on master first.

Isn't one of the most common ways to run into "out of shared memory"
"You might need to increase max_locks_per_transaction." to run pg_dump?
And that's pretty commonly done against standbys?

Greetings,

Andres Freund


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

Предыдущее
От: Fabien COELHO
Дата:
Сообщение: Re: [HACKERS] WIP Patch: Pgbench Serialization and deadlock errors
Следующее
От: Tom Lane
Дата:
Сообщение: Re: StandbyAcquireAccessExclusiveLock doesn't necessarily