What is the index temp_obs_i_obs_id_index on, exactly? Is it a serial
column or some such?
Yup:
Okay, that explains it then. In a serial column's index, essentially
all splits will be on the rightmost page of the tree. This means that
when bt_split tries to get a new free page, it will
I appear to have a hang on my system (40 minutes so far, it's now
17:40). The code is from CVS updated 8/6 if I remember correctly.
The machine is idle, with a vacuum waiting and an INSERT doing nothing.
The vacuum is being generated via pg_autovacuum.
The output from the perl script leading
Robert Creager [EMAIL PROTECTED] writes:
Could you supply the relation names corresponding to the relation OIDs
appearing in pg_locks, so we can be sure who's processing what?
Sure, if you tell me how ;-) I looked at the view definition and that didn't help
me much...
select relname from
Robert Creager [EMAIL PROTECTED] writes:
[much data]
Well, I'm baffled. The vacuum process is evidently waiting for the
insert, but I don't think it could be holding any lock that the other
two want. The insert is trying to grab a per-buffer lock, which is
reasonable. I do not see that the
On Sat, 09 Aug 2003 21:17:05 -0400
Tom Lane [EMAIL PROTECTED] said something like:
Robert Creager [EMAIL PROTECTED] writes:
[much data]
Could you supply the relation names corresponding to the relation OIDs
appearing in pg_locks, so we can be sure who's processing what?
Well, there
On Sat, 09 Aug 2003 20:12:36 -0400
Tom Lane [EMAIL PROTECTED] said something like:
Robert Creager [EMAIL PROTECTED] writes:
Anything to look at before I kick it?
pg_locks and pg_stat_activity, if you can select from them in a
non-stuck backend.
tassiv=# select * from pg_locks;
relation |
On Sat, 09 Aug 2003 21:17:05 -0400
Tom Lane [EMAIL PROTECTED] said something like:
Could you supply the relation names corresponding to the relation OIDs
appearing in pg_locks, so we can be sure who's processing what?
Sure, if you tell me how ;-) I looked at the view definition and that
Robert Creager [EMAIL PROTECTED] writes:
Anything to look at before I kick it?
pg_locks and pg_stat_activity, if you can select from them in a non-stuck
backend.
It's not built with debug, but I
can still get a backtrace.
Might be useful.
regards, tom lane
