thank you all for your help. It was indeed my copy script that
destroyed the database. I now understand that postgresql shouldn't be
concerned with validating a WAL segment, that's the responsibility of
the script that hands the segment to postgres.
-lee
On Fri, Jan 30, 2009 at 9:52 AM, Tom Lane
On Fri, Jan 30, 2009 at 7:52 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Jaume Sabater jsaba...@gmail.com writes:
On Fri, Jan 30, 2009 at 2:22 AM, Tom Lane t...@sss.pgh.pa.us wrote:
We probably should add a caution about this to the manual's discussion
of how to write archiving scripts.
I presume
On Fri, Jan 30, 2009 at 2:22 AM, Tom Lane t...@sss.pgh.pa.us wrote:
We probably should add a caution about this to the manual's discussion
of how to write archiving scripts.
I presume you mean the copy/transfer process did not do its job
correctly, Tom. Therefore, I would advise using a script
I'm new to the list. So hello everyone. This morning my monitoring
system sent me an alert that my warm standby database had exited
recovery mode. I checked on it when I woke up and sure enough, it had
stopped looking for new WAL files and became available for queries.
After some digging, I
Lee Azzarello l...@dropio.com writes:
cp: writing `pg_xlog/./0001002F00AA': No space left on device
2009-01-29 12:48:14 UTC LOG: could not read from log file 47, segment
170, offset 3129344: Success
2009-01-29 12:48:14 UTC LOG: redo done at 2F/AA2FBE08
The bottom line here seems
