Howdy,
I've been finding that keeping full query logs is quite helpful; I started
doing this to be able to run pgbadger each day to get a nice overview of what's
going on with the db servers. The one huge downside to this is that the logs
are so noisy, it's hard to track down errors and stats
I have a smallish Postgres 9.0 database with Primary and Standby instances.
These instances are set up with streaming replication from the Primary to
the Standby. The primary archives WAL files to a shared directory that is
accessible from the Standby. This is a hot standby, so transactions are
As it turns out, it was prepared transactions at fault. I restored my test
bed, forced a rollback and the locks were gone. At least now I can connect
those dots. :-)
On Fri, Feb 22, 2013 at 1:15 AM, Albe Laurenz wrote:
> Ned Wolpert wrote:
> > I'm doing a postmortem on a corruption event we ha
Ned Wolpert wrote:
> I'm doing a postmortem on a corruption event we had. I have an idea on what
> happened, but not sure.
> I figure I'd share what happened and see if I'm close to right here.
>
> Event: Running 9.1.6 with hot-standby, archiving 4 months of wal files, and
> even a nightly p
