| From: | Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com> |
|---|---|
| To: | Atul Kumar <akumar14871(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: strange behavior of WAL files |
| Date: | 2021-06-04 10:56:56 |
| Message-ID: | 20210604125656.47938b0c@firost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 4 Jun 2021 15:39:30 +0530
Atul Kumar <akumar14871(at)gmail(dot)com> wrote:
> HI,
>
> We have a centos 6 enviornment where postgres 9.6 is running on it.
>
> We have strange behavior of WAL files of pg_xlog directory
>
> As we have set archive_command to archive WAL files at different
> location and the archive_command is working fine.
>
> So strange behavior is :
>
> We have a WAL file say for example "00000001000036CD000000E2" of
> 01.06.2021 (1st June 2021) that is getting archive successfully at the
> archive location and once it is archived, this file with same name
> (00000001000036CD000000E2) is getting generated with the latest
> timestamp (as today is 04.06.2021).and all old WAL files are behaving
> in same manner.
What is you archive_command?
I'm not sure I understand correctly, but keep in mind your
archive_command must be "read only". Do not remove the WAL file after archiving
it.
Regards,
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pól Ua Laoínecháin | 2021-06-04 10:58:55 | EXPLAIN (ANALYZE, BUFFERS) - puzzling numbers for a simple query. |
| Previous Message | Atul Kumar | 2021-06-04 10:09:30 | strange behavior of WAL files |