From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
---|---|
To: | "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at> |
Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org>, <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] wal_checksum = on (default) | off |
Date: | 2007-01-05 10:35:47 |
Message-ID: | 1167993347.20749.347.camel@silverbirch.site |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Fri, 2007-01-05 at 11:01 +0100, Zeugswetter Andreas ADI SD wrote:
> > > What's the use-case for changing the variable on the fly anyway? Seems a
> better
> > > solution is just to lock down the setting at postmaster start.
>
> I guess that the use case is more for a WAL based replicate, that
> has/wants a different setting. Maybe we want a WAL entry for the change,
> or force a log switch (so you can interrupt the replicate, change it's
> setting
> and proceed with the next log) ?
>
> Maybe a 3rd mode for replicates that ignores 0 CRC's ?
Well, wal_checksum allows you to have this turned ON for the main server
and OFF on a Warm Standby.
The recovery process doesn't check for postgresql.conf reloads, so
setting it at server start is effectively the same thing in that case.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Zeugswetter Andreas ADI SD | 2007-01-05 11:30:46 | Re: [HACKERS] wal_checksum = on (default) | off |
Previous Message | Zeugswetter Andreas ADI SD | 2007-01-05 10:01:31 | Re: [HACKERS] wal_checksum = on (default) | off |
From | Date | Subject | |
---|---|---|---|
Next Message | Zeugswetter Andreas ADI SD | 2007-01-05 11:30:46 | Re: [HACKERS] wal_checksum = on (default) | off |
Previous Message | Zeugswetter Andreas ADI SD | 2007-01-05 10:01:31 | Re: [HACKERS] wal_checksum = on (default) | off |