RE: Stuck spins in current

From: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: RE: Stuck spins in current
Date: 2001-03-20 00:59:57
Message-ID: 8F4C99C66D04D4118F580090272A7A234D3331@sectorbase1.sectorbase.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> "Vadim Mikheev" <vmikheev(at)sectorbase(dot)com> writes:
> > Anyway, deadlock in my tests are very correlated with new log file
> > creation - something probably is still wrong...
>
> Well, if you can reproduce it easily, seems like you could
> get in there and verify or disprove my theory about where
> the deadlock is.

You were right - deadlock disappeared.

BTW, I've got ~320tps with 50 clients inserting (int4, text[1-256])
records into 50 tables (-B 16384, wal_buffers = 256) on Ultra10
with 512Mb RAM, IDE (clients run on the same host as server).

Vadim

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-03-20 01:08:38 Re: Stuck spins in current
Previous Message Tom Lane 2001-03-20 00:38:36 Re: elog with automatic file, line, and function