| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Francisco Reyes <lists(at)natserv(dot)net> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Large pg_xlog |
| Date: | 2016-09-29 05:36:04 |
| Message-ID: | CAB7nPqRR7AHR3sw-6KeOeYRHePe_UHuiirNweZ96Kc_WMkbwrw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Sep 29, 2016 at 2:25 PM, Francisco Reyes <lists(at)natserv(dot)net> wrote:
> There is no archive_status
>
> ll 9.3/main/pg_xlog/ |grep arch
> postgres(at)s0pdb03:~$
Meh. There must be a folder named archive_status in pg_xlog. Or
something is broken with your installation. Don't you have in your log
files something like that?
LOG: could not create archive status file
"pg_xlog/archive_status/000000010000000000000001.ready": No such file
or directory
That's what you would get if archive_status was for some reason
missing, and pg_xlog would just keep the WAL segments around until its
partition gets full.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Job | 2016-09-29 09:14:06 | Out of memory in pg_bulkload |
| Previous Message | Francisco Reyes | 2016-09-29 05:25:59 | Re: Large pg_xlog |