From: | amacvar <kahitarich-postgresForum(at)yahoo(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: What else could I've done? COPY to unlogged tbl "hung"/locked the table |
Date: | 2012-08-31 18:21:21 |
Message-ID: | 1346437281821-5722162.post@n5.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
In addition here is a backtrace of the process while it hung again today:
(thanks to our SA Eric)
#0 0x000000396c8d4627 in semop () from /lib64/libc.so.6
#1 0x00000000005dc313 in PGSemaphoreLock ()
#2 0x0000000000616586 in LWLockAcquire ()
#3 0x00000000004a718c in ginHeapTupleFastInsert ()
#4 0x000000000049c808 in gininsert ()
#5 0x00000000006dd968 in FunctionCall6Coll ()
#6 0x0000000000474b07 in index_insert ()
#7 0x00000000005664c8 in ExecInsertIndexTuples ()
#8 0x0000000000511fa2 in DoCopy ()
#9 0x0000000000626f71 in standard_ProcessUtility ()
#10 0x0000000000624299 in PostgresMain ()
#11 0x0000000000625309 in CreateQueryDesc ()
#12 0x0000000000625d35 in PortalRun ()
#13 0x0000000000623262 in PostgresMain ()
#14 0x00000000005e7ae4 in ClosePostmasterPorts ()
#15 0x00000000005e8861 in PostmasterMain ()
#16 0x000000000058c5be in main ()
--
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-tp5721983p5722162.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-08-31 19:53:27 | Re: Re: What else could I've done? COPY to unlogged tbl "hung"/locked the table |
Previous Message | amacvar | 2012-08-30 19:16:02 | What else could I've done? COPY to unlogged tbl "hung"/locked the table |