From: | Kieren Scott <kierenscott(at)hotmail(dot)com> |
---|---|
To: | <pgsql-admin(at)postgresql(dot)org> |
Cc: | <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: WAL and archive disks full |
Date: | 2010-08-24 09:39:56 |
Message-ID: | BAY149-w23F492BFF64528E475BB61AE830@phx.gbl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Thank you.
Kieren
> To: kierenscott(at)hotmail(dot)com
> CC: pgsql-admin(at)postgresql(dot)org
> Subject: Re: [ADMIN] WAL and archive disks full
> Date: Mon, 23 Aug 2010 20:17:02 -0400
> From: tgl(at)sss(dot)pgh(dot)pa(dot)us
>
> Kieren Scott <kierenscott(at)hotmail(dot)com> writes:
> > [ hypothetical scenario: ]
> > You can't start the instance because it needs to write to the WAL disk
> > (which is full), but if you manually move WAL files off the WAL disk,
> > the archiver will fail because it can't find WAL files it needs to
> > archive.
>
> Uh, no, that shouldn't be a problem. You can manually move the same WAL
> files that the archiver would move. Look into the
> pg_xlog/archive_status subdirectory. Any WAL files that have a ".ready"
> file in there can be moved to archive, and then you delete the .ready
> file, and you're good to go.
>
> Of course, if you don't have any .ready files, you're going to need to
> look elsewhere for some disk space to reclaim :-(
>
> regards, tom lane
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
From | Date | Subject | |
---|---|---|---|
Next Message | Jens Wilke | 2010-08-24 09:44:14 | Re: Enterprise pg database monitoring |
Previous Message | Kieren Scott | 2010-08-24 09:35:43 | Enterprise pg database monitoring |