Re: Is it really such a good thing for newNode() to be a macro?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Alex Hunsaker" <badalex(at)gmail(dot)com>
Cc: "Peter Eisentraut" <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, "Stephen R(dot) van den Berg" <srb(at)cuci(dot)nl>
Subject: Re: Is it really such a good thing for newNode() to be a macro?
Date: 2008-08-30 02:53:18
Message-ID: 7029.1220064798@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Alex Hunsaker" <badalex(at)gmail(dot)com> writes:
> Hrm, I tried it on my x86_64 (quad core 2.66ghz, sorry no exotic
> machines here :)) and did not see any real noticeable difference
> between the two...

Thanks. That confirms my feeling that I was seeing some weird artifact
on my own x86_64 box.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen R. van den Berg 2008-08-30 10:02:40 Re: Is it really such a good thing for newNode() to be a macro?
Previous Message Brendan Jurd 2008-08-30 01:39:04 to_date() validation