Re: WalSndWakeup() and synchronous_commit=off

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: WalSndWakeup() and synchronous_commit=off
Дата
Msg-id CA+Tgmob81D2Z0z5gZRC3uYJ7Eo1a-3oaiO0oK3Tu2Ki+MWxsMg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: WalSndWakeup() and synchronous_commit=off  (Fujii Masao <masao.fujii@gmail.com>)
Ответы Re: WalSndWakeup() and synchronous_commit=off  (Andres Freund <andres@2ndquadrant.com>)
Re: WalSndWakeup() and synchronous_commit=off  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Дерево обсуждения 
On Fri, May 11, 2012 at 1:09 PM, Fujii Masao <masao.fujii@gmail.com> wrote:
> Calling WalSndWakeup() while WALWriteLock is being held might cause another
> performance degradation. No?

That definitely doesn't seem ideal - a lot of things can pile up
behind WALWriteLock.  I'm not sure how big a problem it would be in
practice, but we generally make a practice of avoiding sending signals
while holding LWLocks whenever possible...

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: PL/perl elog(ERROR) Does not Abort Transaction
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Re: [COMMITTERS] pgsql: Ensure age() returns a stable value rather than the latest value