On Mon, 11 Aug 2003 10:11:37 -0400 Tom Lane <[EMAIL PROTECTED]> said something like:
> Robert Creager <[EMAIL PROTECTED]> writes: > > Opps, if it helps, the log of the deadlock: > > > Aug 10 14:19:36 thunder postgres[18735]: [2-1] ERROR: deadlock detected > > > Aug 10 14:19:36 thunder postgres[18735]: [2-2] DETAIL: Proc 18735 waits > > for AccessExclusiveLock on relation 18028 of database 17140; blocked by > > proc 18815. > > > Aug 10 14:19:36 thunder postgres[18735]: [2-3] Proc 18815 waits for > > AccessExclusiveLock on relation 18101 of database 17140; blocked by proc > > 18735. > > What tables do the two referenced OIDs correspond to? Also, which > process was doing what, exactly? 18028 is table temp_obs_i 18101 is index temp_obs_i_loc_index So, my guess is that 18735 is the vacuum process (likely vacuum analyze, driven from pg_autovacuum), and 188735 is a 'REINDEX INDEX temp_obs_i_loc_index'. Cheers, Rob PS. Please keep CC'ing me, as I'm trying to get re-subscribed to the lists. It looks like I was dropped... -- 08:25:16 up 10 days, 1:10, 4 users, load average: 3.44, 3.49, 3.44
pgp00000.pgp
Description: PGP signature
