Re: danger of stats_temp_directory = /dev/shm
От | Andres Freund |
---|---|
Тема | Re: danger of stats_temp_directory = /dev/shm |
Дата | |
Msg-id | 20130819183950.GA26775@awork2.anarazel.de обсуждение исходный текст |
Ответ на | Re: danger of stats_temp_directory = /dev/shm (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: danger of stats_temp_directory = /dev/shm
|
Список | pgsql-hackers |
On 2013-08-19 14:28:28 -0400, Tom Lane wrote: > One possibility is to do the initial check somewhere shortly after > ChangeToDataDir(), and have the GUC check hook only attempt to make a > check in SIGHUP context. Unfortunately we aren't passing the context to > check hooks, only GucSource which isn't adequate for this. Not sure if we > want to go so far as to change the check-hook API at this point. We could > probably think of some other, klugy way to tell if it's initial startup. Is it even actually safe to have stats_temp_directory PGC_SIGHUP after the per DB splitup? I haven't audited the code for it, but it seems somewhat likely that we would end up with some files in the old and some in the new directory? Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: