Re: XLog changes for 9.3

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: XLog changes for 9.3
Date: 2012-06-07 16:58:59
Message-ID: 201206071859.00048.andres@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thursday, June 07, 2012 06:53:58 PM Tom Lane wrote:
> Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> > dance. If the record can be smeared over two pages there is no point in
> > storing it aligned.
>
> I think this is not true. The value of requiring alignment is that you
> can read the record-length field without first having to copy it somewhere.
> In particular, it will get really ugly if the record length field itself
> could cross a page boundary. I think we want to be able to determine
> the record length before we do any data copying, so that we can malloc
> the record buffer and then just do one copy step.
Hm, I had assumed the record would get copied into a temp/static buffer first
and only get reassembled together with the data afterwards.
But if thats not the way to go, sure, storing it aligned so that the length
can always be read aligned within a page is sensible.

Andres

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2012-06-07 17:03:32 Re: XLog changes for 9.3
Previous Message Simon Riggs 2012-06-07 16:57:07 Re: slow dropping of tables, DropRelFileNodeBuffers, tas