| From: | Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com> |
|---|---|
| To: | Ninad Shah <nshah(dot)postgres(at)gmail(dot)com> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, basti <mailinglist(at)unix-solution(dot)de>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: prevent WAL replication to fill filesystem |
| Date: | 2021-09-08 06:39:03 |
| Message-ID: | 80F8268C-59FD-4C83-8DFD-36281AD912B6@dalibo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Le 8 septembre 2021 06:07:15 GMT+02:00, Ninad Shah <nshah(dot)postgres(at)gmail(dot)com> a écrit :
>These suggestions are appropriate. However, if you are ready to lose your
>replica to keep production running, there are a couple of methods.
>
>1) Set archive_command to "/bin/true"
>2) rename .ready files in archive_status to .done.
You do not need to rename files in archive_status, especially after setting /bin/true. The normal production, if running, will soon enough clean everything, quickly.
A good advice is to never do writes in pg_wal yoursef (mv, rm, edit, etc).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Kass | 2021-09-08 13:20:44 | Re: No xmin in pg_database |
| Previous Message | hubert depesz lubaczewski | 2021-09-08 05:14:53 | Re: Is there any technical reason why "alter table .. set not null" can't use index? |