On Aug 29, 2005, at 1:57 PM, Tom Lane wrote:
You must have CFLAGS set to empty in your build environment, because
configure will certainly default to -O2 if not overridden. It works
fine for me on OS X. Maybe you want to trace through the configure
script and see why it's doing something
On Aug 28, 2005, at 4:00 PM, Tom Lane wrote:
Hmm, can you provide a test case for other people to poke at?
I'l try to put one together as small as I can make it.
The table in question is roughly 22M rows. There are about 8k rows
per timestamp (day granularity).
I see -O2 when
Jeff Trout [EMAIL PROTECTED] writes:
On Aug 28, 2005, at 4:00 PM, Tom Lane wrote:
I see -O2 when building PG (CVS tip) on a fully up-to-date 10.4.2
machine. Maybe something odd in your environment, like a preset
CFLAGS setting?
8.0.3 doesn't have any optimization flags
8.1beta1 doesn't
Jeff Trout [EMAIL PROTECTED] writes:
Tracking ti down a bit timestamp_cmp_internal (The btree was made of
a timestamp and int) was taking a large amount of time -
specifically all the calls it makes to isnan(x). 14.1% in __isnand
Hmm, can you provide a test case for other people to
Well folks, I've been trying to track down why this Athlon 2800
(2.1ghz) has been handing my 2.5ghz G5 its cake. I have a query that
(makes no io - the dataset can live in ram easily) takes about 700ms
on the athlon and about 10 seconds on the G5.
Tracking ti down a bit
