This freezes the whole system even with autovacuum = off in
postgresql.conf. As before, the backends wait on a semop() call.
Fixed. There was a deadlock of LockBufferForCleanup and LockBuffer(SHARE).
Redesign that place to downgrade LockBufferForCleanup to LockBuffer(EXCLUSIVE)
with correction
> I did this four times, sometimes with the variant of adding "set
> enable_bitmapscan to false;" before the explain analyze. In three
> cases the database recovered succesfully after the immediate shutdown;
> in the other case, it crapped out much as described in my original
> email.
Sorry to ke
On Wed, Feb 11, 2009 at 10:03 PM, Robert Haas wrote:
> I'm going to try to reproduce this, but here's approximately what I did.
OK, I've managed to build a reproducible test case. Initial setup is
just as I had before:
> create table foo (id serial, x int[], primary key (id));
> create index fo
While fooling around with the GIN fast insert patch tonight, I managed
to hang my test database. :-(
I'm going to try to reproduce this, but here's approximately what I did.
create table foo (id serial, x int[], primary key (id));
create index foo_gin on foo using gin (x);
insert into foo (x) se
