| From: | David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: WAL for backup |
| Date: | 2014-07-29 19:51:40 |
| Message-ID: | 1406663500456-5813214.post@n5.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
shreesha21 wrote
> Thank you David for the quick response. Appreciate it!
> I am currently running PostgreSQL version 9.3.4.
>
> Actually, when I said 300MB, I was referring to the archive system space.
> So like you suggested, I might have to run pg_basebackup more frequently.
> So are you saying that every time after I run pg_basebackup, if I do
> pg_archivecleanup
> then can I ensure data consistency and reduce the archive storage space?
I am not familiar enough with the specific mechanics to feel comfortable
giving prescriptive advice. The pg_basebackup and associated mandatory WAL
file comprise a full image of the database and any WAL files created before
then can be removed.
David J.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/WAL-for-backup-tp5813194p5813214.html
Sent from the PostgreSQL - novice mailing list archive at Nabble.com.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kartik Singh | 2014-07-30 19:08:52 | |
| Previous Message | Shreesha | 2014-07-29 18:04:30 | Re: WAL for backup |