| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | Rob Nagler <nagler(at)bivio(dot)biz> |
| Cc: | PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: reindex/vacuum locking/performance? |
| Date: | 2003-10-03 22:11:45 |
| Message-ID: | 1065219105.3068.43.camel@tokyo |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Fri, 2003-10-03 at 17:47, Rob Nagler wrote:
> They don't deadlock normally,
> only with reindex and vacuum did I see this behavior.
If you can provide a reproducible example of a deadlock induced by
REINDEX + VACUUM, that would be interesting.
(FWIW, I remember noticing a potential deadlock in the REINDEX code and
posting to -hackers about it, but I've never seen it occur in a
real-world situation...)
> One other question: The reindex seems to lock the table for the entire
> process as opposed to freeing the lock between index rebuilds.
Yeah, I wouldn't be surprised if there is some room for optimizing the
locks that are acquired by REINDEX.
-Neil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dror Matalon | 2003-10-03 22:16:58 | Re: Speeding up Aggregates |
| Previous Message | Rod Taylor | 2003-10-03 22:10:29 | Re: Speeding up Aggregates |