| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Stefan Kaltenbrunner" <stefan(at)kaltenbrunner(dot)cc> |
| Cc: | "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: First steps with 8.3 and autovacuum launcher |
| Date: | 2007-10-01 17:15:08 |
| Message-ID: | 87fy0u92oz.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Stefan Kaltenbrunner" <stefan(at)kaltenbrunner(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Islam Hegazy | 2007-10-01 17:17:47 | Re: adding operators |
| Previous Message | Josh Berkus | 2007-10-01 17:13:41 | Re: [HACKERS] PG on NFS may be just a bad idea |