Re: pg_restore 7.4.7 locks itself out

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alban Hertroys <alban(at)magproductions(dot)nl>
Cc: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_restore 7.4.7 locks itself out
Date: 2006-04-10 15:45:23
Message-ID: 26380.1144683923@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Alban Hertroys <alban(at)magproductions(dot)nl> writes:
> postgres 15092 0.0 0.3 43692 12924 ? D 14:11 0:00 postgres:
> postgres vh3_live [local] INSERT

This process is not blocked on a lock: it's waiting for disk I/O.

Thoughts that come to mind include (1) it's going fine and you're not
patient enough; (2) something wrong with your disk drive; (3) DB is
mounted across NFS and you're having network problems.

> I suppose this may be fixed in a newer version, but our sysadmin'd
> prefer to stay with versions packaged by the distributor (Debian in this
> case).

If your sysadmin wants to use 7.4.7 rather than 7.4.<latest>, he needs
swift application of a cluestick. I'll grant that there might be
application-compatibility reasons to stay on 7.4.*, but not to avoid
being up to date in that release series. See
http://developer.postgresql.org/docs/postgres/release-7-4-12.html
and following pages.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2006-04-10 15:48:07 Re: Meaning of "loops" in EXPLAIN ANALYSE output
Previous Message Martijn van Oosterhout 2006-04-10 15:17:53 Re: Meaning of "loops" in EXPLAIN ANALYSE output