Date: Tue, 4 Sep 2012 21:01:44 -0700 (PDT)
From: amacvar <kahitarich-postgresForum@yahoo.com>
To: pgsql-admin@postgresql.org
Message-ID: <1346817704996-5722754.post@n5.nabble.com>
In-Reply-To: <18243.1346442807@sss.pgh.pa.us>
References: <1346354162985-5721983.post@n5.nabble.com>
	<1346437281821-5722162.post@n5.nabble.com>
	<18243.1346442807@sss.pgh.pa.us>
Subject: Re: What else could I've done? COPY to unlogged tbl "hung"/locked
	the table
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Thank you Tom for the suggestion and the workaround.
I think we will be able to hold off on the temporary workaround.

Would the 2nd processes in the deadlock show up in pg_locks? (It didn't)
An insert from another table that i created to test the datafile did show up
as blocked.
I got confirmation from developers that no other process was running at the
time.

Also, even after a reboot, the COPY to the unlogged table hung, until it was
dropped and recreated.
After the latest occurrence, we took some downtime and I have rebuilt all
unlogged tables, no recurrences yet.


--
View this message in context: http://postgresql.1045698.n5.nabble.com/What-else-could-I-ve-done-COPY-to-unlogged-tbl-hung-locked-the-table-tp5721983p5722754.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.