On 09/29/2016 01:36 AM, Michael Paquier wrote:
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/00010001.ready": No such file
That was the problem.
FATAL:
On Thu, Sep 29, 2016 at 2:25 PM, Francisco Reyes wrote:
> There is no archive_status
>
> ll 9.3/main/pg_xlog/ |grep arch
> postgres@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
On 09/26/2016 09:05 PM, Michael Paquier wrote:
What are the files in pg_xlog/archive_status? Do see a lot of .ready
entries? Perhaps you could de-bloat things by using archive_command =
'/bin/true' (REM on Windows as far as I recall).
There is no archive_status
ll 9.3/main/pg_xlog/ |grep
On Tue, Sep 27, 2016 at 9:26 AM, Francisco Reyes wrote:
> The only times archive command failed I believe is because the volume where
> pg_xlog is ran out of space.
> FATAL: archive command was terminated by signal 3: Quit
>
> There are 2 of those today. So that does not seem
On 09/26/2016 08:08 PM, Andreas Kretschmer wrote:
archive_command failed? If that happens the wal's will not deleted,
you should see error-messages in the log.
The only times archive command failed I believe is because the volume
where pg_xlog is ran out of space.
FATAL: archive command
On 27 September 2016 01:52:26 CEST, Francisco Reyes wrote:
>Any ideas why pg_xlog is going so high?
archive_command failed? If that happens the wal's will not deleted, you should
see error-messages in the log.
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit
Postgresql 9.3
checkpoint_segments=6
wal_keep_segments=300
Machine is master for 2, asynchronous, slaves.
pg_xlog in /var/lib/postgresql/9.3/main/pg_xlog
NFS mount with WAL archiving in /opt/backups/walarchives/HostName
During a load of a file, using copy, the pg_xlog grew to almost 120GB