| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: Potential deadlock with auto-analyze |
| Date: | 2008-06-09 15:24:12 |
| Message-ID: | 20080609152412.GD5026@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> If that's the right diagnosis, we probably ought to try to fix DROP
> INDEX to not do that, since it could deadlock against any number of
> things not just autovac. But there's another question here: can we
> make autovac lose the deadlock war, instead of the user process?
Hmm, I thought autovacuum was already supposed to lose on deadlock.
Perhaps it's only considering VACUUM though and not analyze ... [checks]
nope, that doesn't seem to be it.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-06-09 15:33:19 | Re: pg_dump restore time and Foreign Keys |
| Previous Message | Andrew Dunstan | 2008-06-09 15:23:19 | Re: pg_dump restore time and Foreign Keys |