"scott.marlowe" wrote: > Having a FILE called pg_xlog isn't the fix here, it's the result of the > fix, which is to take all the steps of moving the pg_xlog directory and > put them into one script file the user doesn't need to understand to do it > right. I.e. idiot proof the system as much as possible.
And your script/program cannot modify postgresql.conf instead of creating a new file? Please remember: "A fool with a tool is still a fool". You can provide programs and scripts as many as you want. There have allways been these idiots who did stuff like truncating pg_log ... Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== [EMAIL PROTECTED] # ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org
