Re: [HACKERS] current CVS snapshot of pgsql crash ...

> David Sauer  writes:
> > david=> select textout(byteaout(odata)) from xinv18986;
> > pqReadData() -- backend closed the channel unexpectedly.
> 
> I think this is not related to large objects per se --- it's a
> typechecking failure.  textout is expecting a text datum, and it's
> not getting one because that's not what comes out of byteaout.
> (The proximate cause of the crash is that textout tries to interpret
> the first four bytes of byteaout's output as a varlena length...)
> 
> The parser's typechecking machinery is unable to catch this
> error because textout is declared to take any parameter type
> whatever (its proargtype is 0).
> 
> Why don't the type output functions have the correct input types
> declared for them in pg_proc???
> 
> For that matter, why do we allow user expressions to call the type
> input/output functions at all?  They're not really usable as SQL
> functions AFAICS...

Yes, they take C pointers, don't they.  You can't return one of those in
any SQL function or column name.

--  Bruce Momjian                        |  http://www.op.net/~candle maillist@candle.pha.pa.us            |  (610) 853-3000 +  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026