Re: [HACKERS] initdb should create a warning message [was Re:

2003-12-01 Thread Tilo Schwarz
Greg Stark writes: > Oliver Elphick <[EMAIL PROTECTED]> writes: > > Then it needs to be stated very prominently. But the place to put a > > sign saying "Dangerous cliff edge" is beside the path that leads along > > it.Greg Stark <[EMAIL PROTECTED]>, p > > The only way to make this prominent would

Re: [HACKERS] initdb should create a warning message [was Re:

2003-12-01 Thread Oliver Elphick
On Mon, 2003-12-01 at 16:39, Andrew Dunstan wrote: > Renaming the directories is the only suggestion I've seen that makes > sense. The others remind me of the warning that is now placed on coffee > cup lids at fast food places: "Caution, Contents May Be Hot". I agree that renaming the directorie

Re: [HACKERS] initdb should create a warning message [was Re:

2003-12-01 Thread Andrew Dunstan
Greg Stark wrote: Oliver Elphick <[EMAIL PROTECTED]> writes: Then it needs to be stated very prominently. But the place to put a sign saying "Dangerous cliff edge" is beside the path that leads along it. The only way to make this prominent would be a file with the *name* "THIS DIRECTORY

Re: [HACKERS] initdb should create a warning message [was Re:

2003-12-01 Thread Greg Stark
Oliver Elphick <[EMAIL PROTECTED]> writes: > Then it needs to be stated very prominently. But the place to put a > sign saying "Dangerous cliff edge" is beside the path that leads along > it. The only way to make this prominent would be a file with the *name* "THIS DIRECTORY CONTAINS CRITICAL D

Re: [HACKERS] initdb should create a warning message [was Re: [ADMIN]

2003-12-01 Thread Mike Mascari
Bruce Momjian wrote: > Tom Lane wrote: > >>Oliver Elphick <[EMAIL PROTECTED]> writes: >> >>>On Sun, 2003-11-30 at 23:18, Neil Conway wrote: >>> I do agree that we could stand to document the purpose of pg_clog and pg_xlog more clearly. However, this information belongs in the standard

Re: [HACKERS] initdb should create a warning message [was Re: [ADMIN]

2003-12-01 Thread Bruce Momjian
Tom Lane wrote: > Oliver Elphick <[EMAIL PROTECTED]> writes: > > On Sun, 2003-11-30 at 23:18, Neil Conway wrote: > >> I do agree that we could stand to document the purpose of pg_clog > >> and pg_xlog more clearly. However, this information belongs in the > >> standard documentation, not scattered

Re: [HACKERS] initdb should create a warning message [was Re: [ADMIN] Size on Disk]

2003-12-01 Thread Tom Lane
Oliver Elphick <[EMAIL PROTECTED]> writes: > On Sun, 2003-11-30 at 23:18, Neil Conway wrote: >> I do agree that we could stand to document the purpose of pg_clog >> and pg_xlog more clearly. However, this information belongs in the >> standard documentation, not scattered throughout $PGDATA. > The

Re: [HACKERS] initdb should create a warning message [was Re:

2003-12-01 Thread Oliver Elphick
On Sun, 2003-11-30 at 23:18, Neil Conway wrote: > Oliver Elphick <[EMAIL PROTECTED]> writes: > > The use of the word "log" in the directory name does tend to invite > > this error, and some have acted on it without asking first. I think > > initdb should put a README.IMPORTANT file in $PGDATA to s

Re: [HACKERS] initdb should create a warning message [was Re:

2003-11-30 Thread Neil Conway
Oliver Elphick <[EMAIL PROTECTED]> writes: > The use of the word "log" in the directory name does tend to invite > this error, and some have acted on it without asking first. I think > initdb should put a README.IMPORTANT file in $PGDATA to say [...] If someone deletes something from $PGDATA with

[HACKERS] initdb should create a warning message [was Re: [ADMIN] Size on Disk]

2003-11-30 Thread Oliver Elphick
On Wed, 2003-11-26 at 05:53, Tom Lane wrote: > Grzegorz Dostatni <[EMAIL PROTECTED]> writes: > > Currently the datase is roughly 80 Megs. About half of > > the size is stored in pg_xlog directory. I managed to > > figure out that those files are transaction log files? > > How can I delete them safe