Re: Rethinking stats communication mechanisms

Поиск
Список
Период
Сортировка
От Bort, Paul
Тема Re: Rethinking stats communication mechanisms
Дата
Msg-id DB106B1B5B8F734B8FF3E155A3A556C202D4FBF5@clemail1.tmwsystems.com
обсуждение исходный текст
Ответ на Re: Rethinking stats communication mechanisms  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
>
> * reader's read starts before and ends after writer's update: reader
> will certainly note a change in update counter.
>
> * reader's read starts before and ends within writer's update: reader
> will note a change in update counter.
>
> * reader's read starts within and ends after writer's update: reader
> will note a change in update counter.
>
> * reader's read starts within and ends within writer's update: reader
> will see update counter as odd.
>
> Am I missing anything?
>

The only remaining concern would be the possibility of the reader
thrashing because the writer is updating so often that the reader never
gets the same counter twice. IIRC, the reader was only sampling, not
trying to catch every entry, so that will help. But is it enough?

Regards,
Paul Bort


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

Предыдущее
От: Andrew Dunstan
Дата:
Сообщение: Re: regresssion script hole
Следующее
От: "Giampaolo Tomassoni"
Дата:
Сообщение: R: R: R: Per-server univocal identifier