| From: | tmoore <tmoore(at)ttitech(dot)net> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: TRUNCATE HANGS |
| Date: | 2010-12-04 19:26:54 |
| Message-ID: | 1291490814911-3292403.post@n5.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Can I ask you to elaborate on one of your comments before I move to the
general thread ?
You mention committing the 'idle thread'. The test is not doing
any transaction based work, the write functions just do sql insert, no begin
commit blocks at the application level.
Any tips on interpreting pg_locks ?
Last thing, the test was modified such that only insert and truncate
activity was done, no selects.
No blocking occurred.
Tom
--
View this message in context: http://postgresql.1045698.n5.nabble.com/TRUNCATE-HANGS-tp3292333p3292403.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2010-12-04 19:57:03 | Re: TRUNCATE HANGS |
| Previous Message | Kevin Grittner | 2010-12-04 18:43:54 | Re: TRUNCATE HANGS |