From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Subject: | Re: pg_autovacuum settings not saved on dump |
Date: | 2005-09-20 19:04:31 |
Message-ID: | 20050920190431.GN7630@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Sep 15, 2005 at 11:24:23PM -0400, Tom Lane wrote:
> Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> writes:
> > On Thursday 15 September 2005 15:41, Alvaro Herrera wrote:
> >> Robert Treat reminded me the other day that we don't currently save
> >> pg_autovacuum settings on pg_dump.
>
> > ISTM this is a backwards incompatibility with previous installations that
> > might have used autovacuum from contrib,
>
> How do you figure that? There was no corresponding capability at all in
> previous versions, and pg_dump certainly didn't save any of the contrib
> autovacuum daemon's arguments for you.
Previously the settings would be contained in whatever script the user
was using to start pg_autovacuum, which means they could dump and
restore all day long and not lose any config. This is no longer the
case.
In any case, we should make sure users know about this behavior. I'd be
rather ticked if I did a dump/restore and my settings were suddenly
gone.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2005-09-20 19:15:25 | Re: New dot releases |
Previous Message | Jim C. Nasby | 2005-09-20 17:44:36 | Re: Gerbil build farm failure |