Re: [HACKERS] wal_checksum = on (default) | off

From: "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at>
To: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
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 11:30:46
Message-ID: E1539E0ED7043848906A8FF995BDA57901A358BD@m0143.s-mxs.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches


> > > > 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.

Ok, so when you need CRC's on a replicate (but not on the master) you
turn it
off during standby replay, but turn it on when you start the replicate
for normal operation.

Andreas

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2007-01-05 13:36:24 Last infomask bit
Previous Message Simon Riggs 2007-01-05 10:35:47 Re: [HACKERS] wal_checksum = on (default) | off

Browse pgsql-patches by date

  From Date Subject
Next Message Heikki Linnakangas 2007-01-05 13:36:24 Last infomask bit
Previous Message Simon Riggs 2007-01-05 10:35:47 Re: [HACKERS] wal_checksum = on (default) | off