Re: [GENERAL] Wal logs continued...

[Tom Lane]

Barry Lind <[EMAIL PROTECTED]> writes:
> Given what you say below, I think there is a documentation bug then.  In 
> Section 9.3 of the Administrators Guide it says:

> "After a checkpoint has been made, any log segments written before the 
> redo record are removed, so checkpoints are used to freedisk space 
> in the WAL directory."

Hmm, it should have said "undo record" ...

regards, tom lane

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

[GENERAL] Wal logs continued...

[webb sprague]

Earlier I posted with my problems about the WAL logs eating up all my 
diskspace.  I tried the solutions offered--checkpoint after a big copy and 
shortening the time between flushes.  They helped somewhat.

Unfortunately, the problem snow seems to happen when I vacuum-analyze after a 
big delete.  Even if the vacuum takes more than 2 minutes (the amount of time 
between flushes that I set in postgresql.conf), the logs continue to grow.  
Currently the vacuum has been running for about 20 minutes after a delete of 
about 2,000,000 records out of 5,000,000, and the WAL logs are at about 1.5 G.

Versions: RH 6.2, PG 7.1.1

Is there some way to set the number of log files before a flush/checkpoint 
thing?  We are going to go to a bigger machine next week, but this is quite 
an inconvenience, and it would probably benefit the DB as a whole to place 
some limit on the size of the WAL.

I would code it myself, but I can't yet (next year, after I finish a couple 
of Stevens' books).  If there is any thing else I can do to help, please 
let me know.

Thanks,
W


---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly