Re: Stuck spins in current - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Stuck spins in current
Date
Msg-id 8592.985050518@sss.pgh.pa.us
Whole thread Raw
In response to RE: Stuck spins in current  ("Mikheev, Vadim" <vmikheev@SECTORBASE.COM>)
List pgsql-hackers
"Mikheev, Vadim" <vmikheev@SECTORBASE.COM> writes:
>> "Vadim Mikheev" <vmikheev@sectorbase.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.

Okay, good.  I'll bet the correlation to new-log-file was just because
the WAL insert_lck gets held for a longer time than usual if XLogInsert
is forced to call XLogWrite and that in turn is forced to make a new
log file.  Were you running with wal_files = 0?  The problem would
likely not have shown up at all if logfiles were created in advance...

> 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).

Not bad.  What were you getting before these recent changes?
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Mikheev, Vadim"
Date:
Subject: RE: Stuck spins in current
Next
From: Larry Rosenman
Date:
Subject: Re: elog with automatic file, line, and function