Andres Freund writes:
On 2013-08-19 15:51:16 -0400, Tom Lane wrote:
Yeah, the stats temp directory will act pretty much the same way: there
will be an interval where backends might not get the most up-to-date data,
but it's not clear that it's worth the trouble to get it to be more nearly
synchronous.
Won't it possibly cause stats being entirely lost?
How would that happen? The directory is write-only as far as the stats
collector is concerned, no?

Admittedly it might take a long time for it to write out the data again
for some database that wasn't getting any updates. Possibly it'd be worth
teaching the SIGHUP code segment in the stats collector to check for a
change in the value of stats_temp_directory and schedule write-out for all
databases if that happens.

    regards, tom lane

Search Discussions

Discussion Posts

Previous

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 27 of 32 | next ›
Discussion Overview
grouppgsql-hackers @
categoriespostgresql
postedApr 24, '13 at 11:12p
activeAug 20, '13 at 11:10p
posts32
users9
websitepostgresql.org...
irc#postgresql

People

Translate

site design / logo © 2018 Grokbase