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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Sauer <davids(at)orfinet(dot)cz>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] current CVS snapshot of pgsql crash ...
Date: 1999-06-02 23:51:26
Message-ID: 29400.928367486@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

David Sauer <davids(at)orfinet(dot)cz> 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...

regards, tom lane

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1999-06-03 00:16:59 Re: [HACKERS] current CVS snapshot of pgsql crash ...
Previous Message Tom Lane 1999-06-02 23:35:11 Re: [HACKERS] Re:ORDER BY