Shouldn't have, the only thing we did to the server was restart it and
run our database queries. Clearing out all the wal files from pg_xlog
along with a new base backup did fix it though.
Thanks for the help Tom!
Scot Kreienkamp
skre...@la-z-boy.com
--
Sent via pgsql-general mailing list (pg
"Scot Kreienkamp" writes:
> We have a PG 8.3.7 server that is doing WAL log shipping to 2 other
> servers that are remote mirrors. This has been working well for
almost
> two years. Last night we did some massive data and structure changes
to
> one of our databases. Since then I get these erro
"Scot Kreienkamp" writes:
> I tried to take a new base backup about 45 minutes ago. The master has
> rolled forward a number of WAL files since I last tried, but it still
> fails.
> LOG: restored log file "0001030100FE" from archive
> LOG: restored log file "000103020
"Scot Kreienkamp" writes:
> We have a PG 8.3.7 server that is doing WAL log shipping to 2 other
> servers that are remote mirrors. This has been working well for almost
> two years. Last night we did some massive data and structure changes to
> one of our databases. Since then I get these error