Previously, I had some problems that appear to have been caused by the smp-ppc spinlock issue that was in the early 7.2 series.

The machine is a dual-800 g4, 10.1.5, using a libpq based client through local domain sockets.

The last few days, I've been dealing with a client who has drastically upped their usage of the database and in doing so is causing deadlocks. I was running 7.2 or 7.2.1, I upgraded to a locally compiled 7.2.4. I've run a vacuum full on the databases.

Sometimes the clients have a ps ax status of async_notify, sometimes there's just a stack of selects and updates that get hung. (I'd estimate 6 deadlocks since Saturday). It seems to coincide with times of extra activity, such as when the databases are being backed up with pg_dump.

I've also noticed the following in cron logs from nightly vacuums

NOTICE: Rel pg_attribute: Uninitialized page 59 - fixing
NOTICE: Rel pg_attribute: Uninitialized page 60 - fixing

Is there anything I can do to debug this? I'm willing to give it a shot, but I'm also rapidly preparing a single proc linux/intel machine to take over db duties.


Search Discussions

Discussion Posts

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 1 of 5 | next ›
Discussion Overview
grouppgsql-general @
postedMar 11, '03 at 5:12p
activeMar 13, '03 at 5:07p

2 users in discussion

Eric soroos: 3 posts Tom Lane: 2 posts



site design / logo © 2023 Grokbase