Search Postgresql Archives

Re: Pg_xlog increase due to postgres crash (disk full)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Cliff de Carteret wrote:

> I have now deleted the copy on the remote wal_archive folder and the
> archiving is now functioning and sending the logs from the local to the
> remote folder. The remote database does not startup and the following is in
> the log:
> 
> LOG: database system was shut down in recovery at 2013-01-22 10:54:48 GMT
> LOG: entering standby mode
> LOG: restored log file "00000001000000AB00000051" from archive
> LOG: invalid resource manager ID in primary checkpoint record
> PANIC: could not locate a valid checkpoint record
> LOG: startup process (PID 22350) was terminated by signal 6: Aborted
> LOG: aborting startup due to startup process failure
> 
> 00000001000000AB00000051 is in my remote database's pg_xlog folder

Any chance that there was a pg_start_backup() call on the master without
a matching pg_stop_backup() call?

-Kevin


-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux