--On 25. Januar 2013 20:37:32 -0500 Tom Lane t...@sss.pgh.pa.us wrote:
Don't know how careful pgbtreecheck is. The pg_filedump output isn't
very helpful because you filtered away the flags, so we can't tell if
any of these pages are deleted. (If they are, the duplicate-looking
links might
We are currently analyzing an issue at one of our customers PostgreSQL
database.
The current version is 9.1.6 (update to 9.1.7 is scheduled for next monday,
no downtime possible before). It runs on POWER7 (pSeries 740) on an RHEL6.3
64-bit LPAR. The packages are built from PGDG SVN sources,
On 2013-01-25 16:24:52 +0100, Bernd Helmle wrote:
We are currently analyzing an issue at one of our customers PostgreSQL
database.
The current version is 9.1.6 (update to 9.1.7 is scheduled for next monday,
no downtime possible before). It runs on POWER7 (pSeries 740) on an RHEL6.3
64-bit
--On 25. Januar 2013 16:28:16 +0100 Andres Freund and...@2ndquadrant.com
wrote:
Did you reindex after upgrading to 9.1.6? Did you ever have any crashes
or failovers before upgrading to 9.1.6?
I have seen pretty similar symptoms caused by Fix persistence marking
of shared buffers during WAL
Bernd Helmle maili...@oopsware.de writes:
So i've saved the index file (normal BTree index with a single bigint
column), did a REINDEX and the problem was gone. Looking at the index file
with pg_filedump and pgbtreecheck from Alvaro gave me the following output:
...
Don't know how careful
