| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
| Cc: | "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>, "Brian Hurt" <bhurt(at)janestcapital(dot)com>, "Pg Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Block-level CRC checks |
| Date: | 2008-10-02 15:37:45 |
| Message-ID: | 1822.1222961865@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Jonah H. Harris" <jonah(dot)harris(at)gmail(dot)com> writes:
> Just to see where to go from here... I want to make sure the options
> I've seen in this thread are laid out clearly:
> 1. Hold an exclusive lock on the buffer during the call to smgrwrite
> OR
> 2. Doublebuffer the write
> OR
> 3. Do some crufty magic to ignore hint-bit updates
Right, I think everyone agrees now that #2 seems like the most
preferable option for writing the checksum. However, that still
leaves us lacking a solution for torn pages during a write that
follows a hint bit update. We may end up with some "crufty
magic" anyway for dealing with that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-10-02 15:40:22 | Re: Transactions within a function body |
| Previous Message | Robert Treat | 2008-10-02 15:32:16 | Re: FSM rewrite committed, loose ends |