| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Raghavendra Rao J S V <raghavendrajsv(at)gmail(dot)com> |
| Cc: | Francisco Olarte <folarte(at)peoplecall(dot)com>, Sergei Kornilov <sk(at)zsrv(dot)org>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14963: Number of wal files are keep on increasing |
| Date: | 2017-12-14 10:48:15 |
| Message-ID: | 20171214104815.ldrhdbq6vxfevx7h@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Raghavendra Rao J S V wrote:
> Thank you very much for your explanation.
>
> We are taking the backup of database everyday using pg_basebackup utility. We
> have implemented a pg_basebackup utility through shell script.This will be
> invoked everyday at 2AM and takes the backup of database.
This is a bad idea. If you don't have a very firm grasp of how to write
a backup system, it's better not to write it yourself, because there are
many possible errors you can make that can lead you to end up with
backups that look ok but are actually invalid.
I suggest you use a battle-tested tool such as https://pgbarman.org/ to
do the backups for you. It comes with instructions about what to use in
archive_command, how to take base backups, simple mechanism to remove
old backups, easy to use restore operations, etc.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | skaurus | 2017-12-14 12:31:08 | BUG #14973: hung queries |
| Previous Message | Evgeniy Kozlov | 2017-12-14 07:54:19 | Re: BUG #14972: row duplicate on first SELECT from CTE (by JOIN/FOR UPDATE) from which UPDATE performed recently |