| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Claire McLister <mclister(at)zeesource(dot)net> |
| Cc: | pgsql general list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Create index hanging |
| Date: | 2006-07-21 13:45:44 |
| Message-ID: | 21951.1153489544@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Claire McLister <mclister(at)zeesource(dot)net> writes:
> Yes, that could be the case. We have a python function that imports
> CSV files, which can take a long time, and that may have been running
> during that time. I didn't look at the pg_lock file. What should I be
> looking for?
A record with granted = false for the stuck process (joining pid to
pg_stat_activity will help you determine which process goes with each
record, or look in "ps" output). If you find one, look for a record
for the same lock with granted = true and a conflicting lock type; that
tells you which process is blocking the lock.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Coby | 2006-07-21 14:04:05 | Re: Column info without executing query |
| Previous Message | Martijn van Oosterhout | 2006-07-21 13:34:20 | Re: Column info without executing query |