Re: reducing statistics write overhead - Mailing list pgsql-hackers

From Tom Lane
Subject Re: reducing statistics write overhead
Date
Msg-id 26321.1220740725@sss.pgh.pa.us
Whole thread Raw
In response to Re: reducing statistics write overhead  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: reducing statistics write overhead  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: reducing statistics write overhead  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> As for signalling, maybe we could implement something like we do for the
> postmaster signal stuff: the requestor stores a dbid in shared memory
> and sends a SIGUSR2 to pgstat or some such.

No, no, no.  Martin already had a perfectly sane design for that
direction of signalling: send a special stats message to the collector.
That can carry whatever baggage it needs to.  It's the reverse direction
of "the data you requested is available now, sir" that is tricky.
And I fear that having to keep track of multiple stats-collector output
files would make it very significantly trickier --- both for the stats
collector's own bookkeeping and for the signaling mechanism itself.
I don't believe it's gonna be worth that.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: About that CommitFest redirect page ...
Next
From: Tom Lane
Date:
Subject: Re: About that CommitFest redirect page ...