On Jul 25 2005, ohp@pyrenet.fr wrote:

> Hi Larry,
>
> I'm quitge sure you'll see a problem if you remove --enable-debug
> --enable-cassert from your ./configure

Do we have a clue as to which .c module the compiler/optimizer is (possibly)
screwing up?

I have connections in SCO's compiler group....

(They'll want a small test case )

LER


--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 3535 Gaspar Drive, Dallas, TX 75220-3611


---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

On Mon, 25 Jul 2005, Larry Rosenman wrote:

> Date: 25 Jul 2005 12:47:01 -0500
> From: Larry Rosenman <ler@lerctr.org>
> To: ohp@pyrenet.fr
> Cc: pgsql-hackers list <pgsql-hackers@postgresql.org>
> Subject: Re: [HACKERS] regression failure on latest CVS
>
> On Jul 25 2005, ohp@pyrenet.fr wrote:
>
> > Hi Larry,
> >
> > I'm quitge sure you'll see a problem if you remove --enable-debug
> > --enable-cassert from your ./configure
>
> Do we have a clue as to which .c module the compiler/optimizer is (possibly)
> screwing up?
>
According to Bruce, it's in timestamp.c
Did you get the same problem?
> I have connections in SCO's compiler group....
>
> (They'll want a small test case )
>
> LER
>
>
>

--
Olivier PRENANT Tel: +33-5-61-50-97-00 (Work)
15, Chemin des Monges +33-5-61-50-97-01 (Fax)
31190 AUTERIVE +33-6-07-63-80-64 (GSM)
FRANCE Email: ohp@pyrenet.fr
------------------------------------------------------------------------------
Make your life a dream, make your dream a reality. (St Exupery)

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

ohp@pyrenet.fr wrote:
> On Mon, 25 Jul 2005, Larry Rosenman wrote:
>
>> Date: 25 Jul 2005 12:47:01 -0500
>> From: Larry Rosenman <ler@lerctr.org>
>> To: ohp@pyrenet.fr
>> Cc: pgsql-hackers list <pgsql-hackers@postgresql.org>
>> Subject: Re: [HACKERS] regression failure on latest CVS
>>
>> On Jul 25 2005, ohp@pyrenet.fr wrote:
>>
>>> Hi Larry,
>>>
>>> I'm quitge sure you'll see a problem if you remove --enable-debug
>>> --enable-cassert from your ./configure
>>


For those following along at home:

Removing --enable-cassert and --enable-debug from the options causes
Firefly to fail.

I'm forcing a run with --enable-cassert only, to see what happens (per
request from SCO).

I've saved off the first failure to send to SCO.



--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 3535 Gaspar Drive, Dallas, TX 75220-3611 US


---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Larry Rosenman wrote:

>ohp@pyrenet.fr wrote:
>
>
>>On Mon, 25 Jul 2005, Larry Rosenman wrote:
>>
>>
>>
>>>Date: 25 Jul 2005 12:47:01 -0500
>>>From: Larry Rosenman <ler@lerctr.org>
>>>To: ohp@pyrenet.fr
>>>Cc: pgsql-hackers list <pgsql-hackers@postgresql.org>
>>>Subject: Re: [HACKERS] regression failure on latest CVS
>>>
>>>On Jul 25 2005, ohp@pyrenet.fr wrote:
>>>
>>>
>>>
>>>>Hi Larry,
>>>>
>>>>I'm quitge sure you'll see a problem if you remove --enable-debug
>>>>--enable-cassert from your ./configure
>>>>
>>>>
>
>
>For those following along at home:
>
>Removing --enable-cassert and --enable-debug from the options causes
>Firefly to fail.
>
>I'm forcing a run with --enable-cassert only, to see what happens (per
>request from SCO).
>
>I've saved off the first failure to send to SCO.
>
>
>

I assume that in the SCO compiler turning debugging on turns
optimisation off? If so, that would at least make some kind of sense
(i.e. this would a case of bad optimisation).

cheers

andrew

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

Larry Rosenman wrote:
> ohp@pyrenet.fr wrote:
>> On Mon, 25 Jul 2005, Larry Rosenman wrote:
>>
>>> Date: 25 Jul 2005 12:47:01 -0500
>>> From: Larry Rosenman <ler@lerctr.org>
>>> To: ohp@pyrenet.fr
>>> Cc: pgsql-hackers list <pgsql-hackers@postgresql.org>
>>> Subject: Re: [HACKERS] regression failure on latest CVS
>>>
>>> On Jul 25 2005, ohp@pyrenet.fr wrote:
>>>
>>>> Hi Larry,
>>>>
>>>> I'm quitge sure you'll see a problem if you remove --enable-debug
>>>> --enable-cassert from your ./configure
>>>
>
>
> For those following along at home:
>
> Removing --enable-cassert and --enable-debug from the options causes
> Firefly to fail.
>
> I'm forcing a run with --enable-cassert only, to see what happens
> (per request from SCO).
>
> I've saved off the first failure to send to SCO.

Just --enable-cassert fails as well. SCO also asked if 8.0-STABLE also has
issues. Running
That test now.

LER


--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 3535 Gaspar Drive, Dallas, TX 75220-3611 US


---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

"Larry Rosenman" <ler@lerctr.org> writes:
> For those following along at home:

> Removing --enable-cassert and --enable-debug from the options causes
> Firefly to fail.

FWIW, I just checked that CVS tip works OK for me without these options,
with either integer or float timestamps. I don't see any new warnings,
either. It could well be that the recent changes have introduced some
portability problem in the interval code, but someone's going to have to
actually dig for it :-(

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Tom Lane wrote:
> "Larry Rosenman" <ler@lerctr.org> writes:
>> For those following along at home:
>
>> Removing --enable-cassert and --enable-debug from the options causes
>> Firefly to fail.
>
> FWIW, I just checked that CVS tip works OK for me without these
> options, with either integer or float timestamps. I don't see any
> new warnings, either. It could well be that the recent changes have
> introduced some portability problem in the interval code, but
> someone's going to have to actually dig for it :-(
>
> regards, tom lane

Thanks, Tom. I've reported my findings to the compiler
Guys at SCO. We'll see what they say tomorrow.

LER


--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 3535 Gaspar Drive, Dallas, TX 75220-3611 US


---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

On Mon, 25 Jul 2005, Tom Lane wrote:

> Date: Mon, 25 Jul 2005 23:26:20 -0400
> From: Tom Lane <tgl@sss.pgh.pa.us>
> To: Larry Rosenman <ler@lerctr.org>
> Cc: ohp@pyrenet.fr, 'pgsql-hackers list' <pgsql-hackers@postgresql.org>
> Subject: Re: [HACKERS] regression failure on latest CVS
>
> "Larry Rosenman" <ler@lerctr.org> writes:
> > For those following along at home:
>
> > Removing --enable-cassert and --enable-debug from the options causes
> > Firefly to fail.
>
> FWIW, I just checked that CVS tip works OK for me without these options,
> with either integer or float timestamps. I don't see any new warnings,
> either.
> It could well be that the recent changes have introduced some
> portability problem in the interval code, but someone's going to have to
> actually dig for it :-(
>
That's my feeling but I have no clue where to start.
I know this was introduced at the end of last week.

> regards, tom lane
>
>

--
Olivier PRENANT Tel: +33-5-61-50-97-00 (Work)
15, Chemin des Monges +33-5-61-50-97-01 (Fax)
31190 AUTERIVE +33-6-07-63-80-64 (GSM)
FRANCE Email: ohp@pyrenet.fr
------------------------------------------------------------------------------
Make your life a dream, make your dream a reality. (St Exupery)

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match