Re: pg_xlog -> pg_xjournal? - Mailing list pgsql-hackers

From Christian Ullrich
Subject Re: pg_xlog -> pg_xjournal?
Date
Msg-id mkkp6d$hac$1@ger.gmane.org
Whole thread Raw
In response to pg_xlog -> pg_xjournal?  (Joel Jacobson <joel@trustly.com>)
List 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-expertsusing 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 beclear enough, if a tad long for deeply nested
PGDATAlocations.


Symlinking the old path to the new one would be impossible, ofcourse, if the intent is to protect against "rm -rf
*log*/*"fiends.

-- 

Christian




pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: checkpointer continuous flushing
Next
From: Andres Freund
Date:
Subject: Re: Re: [GENERAL] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1