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. Then it

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 throughout

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 documentation, not

[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 safely? You