From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: danger of stats_temp_directory = /dev/shm |
Date: | 2013-08-19 19:25:38 |
Message-ID: | 25478.1376940338@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> Hm. Is a check like that actually sufficient? The idea of setting
> stats_temp_directory to /dev/shm/postgres or similar in all of several
> clusters on one machine doesn't seem to be that far fetched.
Hm. We could fairly easily have the lockfile management code also
write a postmaster.pid file into the stats_temp_directory, thus claiming
it in the same way as we do the $PGDATA dir itself. Not sure it's worth
the trouble though, since we've not heard any field reports of this sort
of thing.
I note BTW that similar complaints could be lodged against the
log_directory setting. We've not worried about that one too much.
Maybe we're overreacting to this issue for stats_temp_directory,
and tightening up the deletion code is a sufficient fix.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2013-08-19 19:36:26 | Re: danger of stats_temp_directory = /dev/shm |
Previous Message | Karol Trzcionka | 2013-08-19 19:21:53 | Re: GSOC13 proposal - extend RETURNING syntax |