Re: [PATCHES] equal() perf tweak

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] equal() perf tweak
Date: 2003-11-04 17:31:21
Message-ID: 23040.1067967081@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Just a thought - if we are messing with the List definition should we at
> the same time address the strict aliasing issues arising from Node's
> multiple personalities (I think it is the main offender).

> Or is the intention never to do this, or not any time soon?

I have no intention of messing with the Node concept; it's built into
the backend far too firmly to consider any significant change.

I don't think we understand exactly what we'd have to avoid in order to
enable strict aliasing, but if it requires getting rid of Node then it
ain't happening. (I doubt that it does, anyway. I think the issues are
probably quite localized. The main problem I see is that we don't have
any trustworthy check to find out everyplace that strict aliasing could
cause problems.)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Browne 2003-11-04 17:32:29 RC1 on AIX - Some Anti-results
Previous Message Tom Lane 2003-11-04 17:11:16 Re: Experimental patch for inter-page delay in VACUUM

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Dunstan 2003-11-04 18:51:41 Re: [PATCHES] equal() perf tweak
Previous Message Andrew Dunstan 2003-11-04 17:06:33 Re: [PATCHES] equal() perf tweak