Re: TRUNCATE HANGS - Mailing list pgsql-bugs

From Kevin Grittner
Subject Re: TRUNCATE HANGS
Date
Msg-id 4CFA67B402000025000382C8@gw.wicourts.gov
Whole thread Raw
In response to TRUNCATE HANGS  (tmoore <tmoore@ttitech.net>)
Responses Re: TRUNCATE HANGS
List pgsql-bugs
tmoore  wrote:

> I'm a little tired. I just indicated autocommit false, that was
> incorrect.  Autocommit is true.

I would double-check that.  As I said, what you showed us indicates
that something logging in through TCP on localhost is using
transactions, and not committing them when needed.

> Three threads of executions, java writer, java reader, and psql via
> cron for truncation. As an experiment, the java reader was disabled
> and the test did not block.

TRUNCATE will block or be blocked by just about anything, read or
write.  A reading transaction won't release the conflicting lock
until the transaction ends.

-Kevin

pgsql-bugs by date:

Previous
From: tmoore
Date:
Subject: Re: TRUNCATE HANGS
Next
From: "Adrian Klaver"
Date:
Subject: BUG #5783: plpythonu bool behavior change