Re: Rethinking stats communication mechanisms - Mailing list pgsql-hackers

From Bort, Paul
Subject Re: Rethinking stats communication mechanisms
Date
Msg-id DB106B1B5B8F734B8FF3E155A3A556C202D4FBF5@clemail1.tmwsystems.com
Whole thread Raw
In response to Re: Rethinking stats communication mechanisms  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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 by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: regresssion script hole
Next
From: "Giampaolo Tomassoni"
Date:
Subject: R: R: R: Per-server univocal identifier