Re: WIP checksums patch - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: WIP checksums patch
Date
Msg-id 1349108743.15580.44.camel@jdavis
Whole thread Raw
In response to Re: WIP checksums patch  (Bruce Momjian <bruce@momjian.us>)
Responses Re: WIP checksums patch
List pgsql-hackers
On Mon, 2012-10-01 at 10:43 -0400, Bruce Momjian wrote:
> >   The default is <literal>off</> for backwards compatibility and
> >   to allow upgrade. The recommended setting is <literal>on</> though
> >   this should not be enabled until upgrade is successfully complete
> >   with full set of new backups.
> > 
> > I don't understand what that means -- if they have the page_checksums
> > GUC available, then surely upgrade is complete, right? And what is the
> > backwards-compatibility issue?

> I think this need to clearly state "pg_upgrade", not a dump/restore
> upgrade, which would be fine.  It would be interesting to have
> pg_upgrade change this setting, or tell the user to change it.  I am not
> sure enough people are using pg_upgrade to change a default value.

I still don't understand why pg_upgrade and page_checksums don't mix.

Regards,Jeff Davis





pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Hash id in pg_stat_statements
Next
From: Bruce Momjian
Date:
Subject: Re: WIP checksums patch