Re: danger of stats_temp_directory = /dev/shm - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: danger of stats_temp_directory = /dev/shm
Date
Msg-id 52127639.20301@agliodbs.com
Whole thread Raw
In response to Re: danger of stats_temp_directory = /dev/shm  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: danger of stats_temp_directory = /dev/shm  (Andres Freund <andres@2ndquadrant.com>)
Re: danger of stats_temp_directory = /dev/shm  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom,

> I note BTW that similar complaints could be lodged against the
> log_directory setting.  We've not worried about that one too much.

Actually, it does happen that when you change log_directory on a reload,
stuff takes an uneven amount of time to "cut over"; that is, there's a
few seconds while you're writing to both logs at once.  Materially,
though, this isn't a serious operational issue (the logs are known to be
asynchronous), so beyond confusing newbies, it's not something we'd want
to fix.

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: 9.4 regression
Next
From: Andres Freund
Date:
Subject: Re: danger of stats_temp_directory = /dev/shm