| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Curtis Faith" <curtis(at)galtair(dot)com> |
| Cc: | "Pgsql-Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Analysis of ganged WAL writes |
| Date: | 2002-10-08 14:41:43 |
| Message-ID: | 1976.1034088103@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Curtis Faith" <curtis(at)galtair(dot)com> writes:
> Successive writes would write different NON-OVERLAPPING sections of the
> same log buffer. It wouldn't make sense to send three separate copies of
> the entire block. That could indeed cause problems.
So you're going to undo the code's present property that all writes are
block-sized? Aren't you worried about incurring page-in reads because
the kernel can't know that we don't care about data beyond what we've
written so far in the block?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shridhar Daithankar | 2002-10-08 14:41:47 | Re: [GENERAL] Large databases, performance |
| Previous Message | Tom Lane | 2002-10-08 14:38:02 | Re: [GENERAL] Large databases, performance |