| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Scott Whitney <swhitney(at)journyx(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Strange deadlock error last night |
| Date: | 2009-01-13 22:04:13 |
| Message-ID: | 20090113220413.GI4005@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Tom Lane wrote:
> "Scott Whitney" <swhitney(at)journyx(dot)com> writes:
> > It ended up locking up about 250 customer databases until I restarted the
> > postmaster. This is version 8.1.4. Upgrading right now (even to a minor rev)
> > is not really an option.
>
> Not related to the immediate problem, but: you really need to schedule
> 5 minutes' downtime so you can update to 8.1.latest. Reasons can be
> found here:
> http://www.postgresql.org/docs/8.1/static/release.html
Particularly so if you run autovacuum, because otherwise you'll be hit
by a bug fixed in 8.1.6 about template0 being unfrozen (thawed?)
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2009-01-13 22:16:18 | Re: Strange deadlock error last night |
| Previous Message | tyrrill_ed | 2009-01-13 21:38:12 | Problem with pg_dump |