Re: Out of space situation and WAL log pre-allocation (was Tablespaces)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: simon(at)2ndquadrant(dot)com, "'Gavin Sherry'" <swm(at)linuxworld(dot)com(dot)au>, tswan(at)idigx(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Out of space situation and WAL log pre-allocation (was Tablespaces)
Date: 2004-03-03 04:55:03
Message-ID: 8478.1078289703@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joe Conway <mail(at)joeconway(dot)com> writes:
> Tom Lane wrote:
>> facing the possibility of an out-of-WAL-space panic. I suspect that we
>> cannot really do anything about that, but it's annoying. Any bright
>> ideas out there?

> Maybe specify an archive location (that of course could be on a separate
> partition) that the external archiver should check in addition to the
> normal WAL location. At some predetermined interval, push WAL log
> segments no longer needed to the archive location.

Does that really help? The panic happens when you fill the "normal" and
"archive" partitions, how's that different from one partition?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-03-03 04:59:55 Re: Tablespaces
Previous Message Gavin Sherry 2004-03-03 04:46:55 Re: Tablespaces