| From: | John Scalia <jayknowsunix(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | WAL segment management on a standby |
| Date: | 2014-07-11 16:49:46 |
| Message-ID: | 53C015AA.5070908@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Again, thanks to all to have assisted me with getting the WAL segments to both my standby servers. Everything with that is now working quite well. I do have a related followup
question, however. On these standby's nothing is built in to manage those WAL segments in the archive directory. Thus, that directory can grow to the point where it fills up the
disk rather quickly. Any good strategies for dealing with the WAL segments that get put in there. Do I really need them after postgresql has copied them up into the pg_xlog
directory? If so, how far back should I keep them? Yes, I know about keeping everything between backups. So, if my directory looks like:
00000000300000000C000000A1
00000000300000000C000000A2
00000000300000000C000000A3
00000000300000000C000000A3.backup
00000000300000000C000000A4
Could I safely delete the *A1, *A2, and maybe even the *A3 files?
--
Jay
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matheus de Oliveira | 2014-07-11 16:58:08 | Re: WAL segment management on a standby |
| Previous Message | Devrim Gündüz | 2014-07-11 14:04:18 | Re: postgresql checking return status of archive_command? |