From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
Cc: | "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: fmgr changes not yet ported to AIX |
Date: | 2000-07-11 16:13:57 |
Message-ID: | 1151.963332037@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> writes:
> Just wanted to give a short message, that current snapshot does not
> compile on AIX due to the fmgr changes.
Without more details, that's completely unhelpful.
> What exactly does it gain except masking badly written code
> (casts to wrong datatype like ints to longs) that goof the optimizers and
> 64bit ports
> and solving the null value problem ?
> My ideas would be:
> - multi row returns
> - multi column returns (not opaque)
I've said before and I'll say it again: all I'm doing in this round is
fixing our portability and NULL-value problems. Better handling of sets
and tuples is a higher-level problem. If you want to start working on
that, be my guest...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Karel Zak | 2000-07-11 16:22:30 | Re: Distribution making |
Previous Message | Bruce Momjian | 2000-07-11 16:03:57 | Re: [HACKERS] Foreign key bugs (Re: "New" bug?? Serious - crashes backend.) |