| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Renaming of pg_xlog and pg_clog |
| Date: | 2016-08-26 21:15:41 |
| Message-ID: | 4616c35f-7399-cf1d-3e5a-c5ff7b993729@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 8/26/16 4:02 PM, Joshua D. Drake wrote:
> Although... wouldn't run be under var?
Traditionally yes, but things are changing in this area, if you consider
the top-level file system of a modern Linux distribution. One reason is
that "run" is/can be blown away at reboot. This wouldn't be an entirely
useless feature for postgres: Can you tell otherwise which of the
various pid/lock/opts files you can delete if you have killed the
processes and want to eliminate any left-over state? Is postmaster.opts
a configuration file or a state file?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-08-26 21:17:25 | Re: Why is a newly created index contains the invalid LSN? |
| Previous Message | Kevin Grittner | 2016-08-26 21:13:07 | Re: Why is a newly created index contains the invalid LSN? |