Re: lock_timeout GUC patch

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: lock_timeout GUC patch
Дата
Msg-id 8675.1264090110@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: lock_timeout GUC patch  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Thu, Jan 21, 2010 at 10:59 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Why is this a good idea at all? �I can easily see somebody feeling that
>> he'd like autovacuums to fail rather than block on locks for a long
>> time, for example.

> What I can see happening is someone setting this GUC in
> postgresql.conf and then being surprised that it applied to thinks
> like walreceiver and autovacuum, in addition to user queries.  Are we
> even sure that that code would all behave sanely with this behavior?

No, I'm not sure, as I said before ;-).  But a 100%-arbitrary
restriction like "it doesn't apply to background processes" will not
make it noticeably safer.  There is very damn little code that only
executes in background and never anywhere else.
        regards, tom lane


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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: About "Our CLUSTER implementation is pessimal" patch
Следующее
От: Boszormenyi Zoltan
Дата:
Сообщение: Re: lock_timeout GUC patch