| Subject: | Re: Is it really such a good thing for newNode() to be a macro? |
|---|---|
| From: | Tom Lane |
| Date: | Fri, 29 Aug 2008 22:53:18 -0400 |
| Newsgroups: | pgsql.hackers |
"Alex Hunsaker" <badalex@xxxxxxxxx> 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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
|
| Previous by Date: | Re: Is it really such a good thing for newNode() to be a macro?, "Alex Hunsaker" |
|---|---|
| Next by Date: | Re: Is it really such a good thing for newNode() to be a macro?, "Stephen R. van den Berg" |
| Previous by Thread: | Re: Is it really such a good thing for newNode() to be a macro?, "Alex Hunsaker" |
| Next by Thread: | Re: Is it really such a good thing for newNode() to be a macro?, "Heikki Linnakangas" |
| Indexes: | [Date] [Thread] [Top] [All Lists] |