| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Daniel Farina <daniel(at)heroku(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #6170: hot standby wedging on full-WAL disk |
| Date: | 2011-08-25 16:11:35 |
| Message-ID: | CA+Tgmoa_gycDVqH088gqYrsUF=gO_x-Df3hgvTS1Gxm2orKJnA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Aug 22, 2011 at 2:57 AM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> So the problem is that walreceiver merrily writes so much future WAL that it
> runs out of disk space? A limit on the maximum number of future WAL files to
> stream ahead would fix that, but I can't get very excited about it. Usually
> you do want to stream as much ahead as you can, to ensure that the WAL is
> safely on disk on the standby, in case the master dies. So the limit would
> need to be configurable.
It seems like perhaps what we really need is a way to make replaying
WAL (and getting rid of now-unneeded segments) to take priority over
getting new ones.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2011-08-25 17:14:28 | Re: BUG #6177: Size field type TEXT |
| Previous Message | Chander Ganesan | 2011-08-25 15:09:30 | Re: BUG #6176: pg_dump dumps pg_catalog tables |