From: | Christian Ullrich <chris(at)chrullrich(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_xlog -> pg_xjournal? |
Date: | 2015-06-02 17:29:48 |
Message-ID: | mkkp6d$hac$1@ger.gmane.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Michael Nolan wrote:
> Why not take a simpler approach and create a zero length file in directories that should not be fiddled with by non-experts using a file name something like "DO.NOT.DELETE.THESE.FILES"?
Move the critical things into a new subdirectory?
$PGDATA/pg_critical/pg_xlog? Perhaps "pg_internal" instead, or
"pg_indispensable", or "pg_here_be_dragons", or
"pg_delete_this_or_anything_in_here_and_you_wil
l_have_utterly_destroyed_your_database"? That last one should be
clear enough, if a tad long for deeply nested PGDATA
locations.
Symlinking the old path to the new one would be impossible, of
course, if the intent is to protect against "rm -rf *log*/*"
fiends.
--
Christian
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2015-06-02 17:46:08 | Re: Re: [GENERAL] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1 |
Previous Message | Fabien COELHO | 2015-06-02 16:59:05 | Re: checkpointer continuous flushing |