On Wed, 4 Nov 2009, Greg Smith wrote:
On Wed, 4 Nov 2009, Michal Bicz wrote:
Now it is saying constantly in log :
2009-11-04 04:57:39 PST : ERROR: XX000: xlog flush request 2FB/28CE63A8 is
not satisfied --- flushed only to 2FB/8FFEA60
2009-11-04 04:57:39 PST : CONTEXT: writing block 874937 of relation
1663/20863/21548
2009-11-04 04:57:39 PST : LOCATION: XLogFlush, xlog.c:1865
I think you can run into this if disk space on the xlog drive fills up, which
is easy to do with complicated WAL shipping setups if you're not careful.
You might want to double-check that, and check for general disk I/O errors
too.
Looks like Michal's response didn't go on-list, for anyone wandering what
the resolution was he says:
"Thanks but this is apparently is neither badblock nor space limits.
I recreated scenario and apparently warm standby server is set to be
respawned every time it is seen stopped.. That caused data to become
corrupted."
--
* Greg Smith gsmith@xxxxxxxxxxxxx http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
