* 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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
