Re: Proposal: Log inability to lock pages during vacuum

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: Proposal: Log inability to lock pages during vacuum
Дата
Msg-id 20141110172830.GB1791@alvin.alvh.no-ip.org
обсуждение исходный текст
Ответ на Re: Proposal: Log inability to lock pages during vacuum  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Ответы Re: Proposal: Log inability to lock pages during vacuum  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Re: Proposal: Log inability to lock pages during vacuum  (Andres Freund <andres@2ndquadrant.com>)
Список pgsql-hackers
Jim Nasby wrote:
> On 11/7/14, 8:21 PM, Robert Haas wrote:
> >On Thu, Nov 6, 2014 at 8:03 PM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
> >>The problem right now is there's no way to actually obtain evidence that
> >>this is (or isn't) something to worry about, because we just silently skip
> >>pages. If we had any kind of tracking on this we could stop guessing. :(
> >
> >I could see logging it, but I agree with Andres and Alvaro that the
> >odds are strongly against there being any actual problem here.
> 
> I'm fine with that. Any other objections? Andres?

If what we want is to quantify the extent of the issue, would it be more
convenient to save counters to pgstat?  Vacuum already sends pgstat
messages, so there's no additional traffic there.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



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

Предыдущее
От: Magnus Hagander
Дата:
Сообщение: Re: remove pg_standby?
Следующее
От: Fujii Masao
Дата:
Сообщение: Re: PENDING_LIST_CLEANUP_SIZE - maximum size of GIN pending list Re: HEAD seems to generate larger WAL regarding GIN index