Re: First steps with 8.3 and autovacuum launcher - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: First steps with 8.3 and autovacuum launcher
Date
Msg-id 87fy0u92oz.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: First steps with 8.3 and autovacuum launcher  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
Responses Re: First steps with 8.3 and autovacuum launcher
Re: First steps with 8.3 and autovacuum launcher
List pgsql-hackers
"Stefan Kaltenbrunner" <stefan@kaltenbrunner.cc> writes:

> some additional datapoints:
>
> autovacuum on, delay 20: 8h 40min
> autovacuum on, delay 0: 4h 23min


I realize this isn't directly addressing the problem but perhaps part of the
solution would be to start advocating the use of pg_restore -1 ? That would
solve the problem for the narrow case of pg_restore.

In the long run we could think about exposing some kind of command for
pg_restore to use which would disable autovacuum from touching a table. (Or
take a session-level lock on the table -- shudder)

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: PG on NFS may be just a bad idea
Next
From: Tom Lane
Date:
Subject: Re: Enforcing database encoding and locale match