Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-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

pgsql-hackers by date

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

pgsql-patches by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group