When will CVSup be upgraded? I continue to see
that you have the time bug. I just ran cvsup and got:
Parsing supfile "cvsup_config"
Connecting to postgresql.org
Connected to postgresql.org
Server software version: REL_16_1
Server postgresql.org has the S1G bug
See http://www.polstra.com/project
OK, I see a patch from 2001-09-10 for parse_target.c which is a smoking
gun. The patch tries to force a column name for the TypeCast node, and
doesn't check to see if one was actually specified :(
So that probably explains why, on my system,
select cast(int4 '1' as float8);
fails, while
se
> Nope, these variants all work for me. But I know where the problem is
> now: you have a broken version of FigureColname() in parse_target.c.
> Somebody submitted a bogus patch last week; I've fixed it in current
> CVS, but evidently your sources are from last week.
Sure. cvsup needed to be upg
> > #2 0x806cb34 in TupleDescInitEntry (desc=0x82d6304, attributeNumber=1,
> > attributeName=0x1f8 , oidtypeid=1184,
> > typmod=-1, attdim=0,
> > attisset=0 '\000') at tupdesc.c:365
> This appears to indicate that you have a Resdom node with an invalid
> resname field. Seems like that wo
Thomas Lockhart <[EMAIL PROTECTED]> writes:
> #2 0x806cb34 in TupleDescInitEntry (desc=0x82d6304, attributeNumber=1,
> attributeName=0x1f8 , oidtypeid=1184,
> typmod=-1, attdim=0,
> attisset=0 '\000') at tupdesc.c:365
This appears to indicate that you have a Resdom node with an invalid
I have split the timestamp data type into two types to better match
SQL9x specs. I've implemented them as "timestamp" and "timestamptz" (the
latter corresponding to the implementation in recent releases), and have
implemented conversion routines between the two types. However, I expect
to be able
