Re: XLByte* usage

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: XLByte* usage
Date: 2012-12-28 17:59:50
Message-ID: 20121228175950.GB4150@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund escribió:
> On 2012-12-17 13:16:47 -0500, Tom Lane wrote:
> > Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> > > On 2012-12-17 12:47:41 -0500, Tom Lane wrote:
> > >> But, if the day ever comes when 64 bits doesn't seem like enough, I bet
> > >> we'd move to 128-bit integers, which will surely be available on all
> > >> platforms by then. So +1 for using plain comparisons --- in fact, I'd
> > >> vote for running around and ripping out the macros altogether. I had
> > >> already been thinking of fixing the places that are still using memset
> > >> to initialize XLRecPtrs to "invalid".
> >
> > > I thought about that and had guessed you would be against it because it
> > > would cause useless diversion of the branches? Otherwise I am all for
> > > it.
> >
> > That's the only argument I can see against doing it --- but Heikki's
> > patch was already pretty invasive in the same areas this would touch,
> > so I'm thinking this won't make back-patching much worse.
>
> I thought a while about this for while and decided its worth trying to
> this before the next review round of xlogreader.

I have applied these three patches, after merging for recent changes.
Thanks.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Charles Gomes 2012-12-28 18:06:44 Whats the correct way to change trigdata->tg_relation
Previous Message Peter Geoghegan 2012-12-28 17:58:53 Re: pg_stat_statements: calls under-estimation propagation