| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: wal_checksum = on (default) | off |
| Date: | 2007-01-04 16:09:59 |
| Message-ID: | 17558.1167926999@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
"Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> On Thu, 2007-01-04 at 10:00 -0500, Tom Lane wrote:
>> "Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
>>> Recovery can occur with/without same setting of wal_checksum, to avoid
>>> complications from crashes immediately after turning GUC on.
>>
>> Surely not. Otherwise even the "on" setting is not really a defense.
> Only when the CRC is exactly zero, which happens very very rarely.
"It works most of the time" doesn't exactly satisfy me. 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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2007-01-04 16:13:32 | Re: Tabs or Spaces |
| Previous Message | Simon Riggs | 2007-01-04 15:56:39 | Re: wal_checksum = on (default) | off |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-01-04 16:30:28 | Re: Assorted typos |
| Previous Message | Simon Riggs | 2007-01-04 15:56:39 | Re: wal_checksum = on (default) | off |