Re: select cash_out('2'); crashes backend on 7.0.2

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: mark(at)summersault(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: select cash_out('2'); crashes backend on 7.0.2
Date: 2000-12-12 20:25:47
Message-ID: 3219.976652747@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>> cascade=> select cash_out(2);
>> pqReadData() -- backend closed the channel unexpectedly.

> I can confirm this is crashes in 7.1 too.

You can get this sort of result with almost any input or output function
:-(. The problem is that they're mostly misdeclared to take type
"opaque", which for no good reason is also considered to mean "accepts
any input type whatever", which means you can pass a value of any type
at all to an input or output function.

There have been some past discussions about introducing a little more
rigor into the type system's handling of I/O functions, but it ain't
gonna happen for 7.1 ...

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2000-12-12 20:28:05 Re: select cash_out('2'); crashes backend on 7.0.2
Previous Message Stephan Szabo 2000-12-12 19:40:35 Re: constrains of array

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2000-12-12 20:28:05 Re: select cash_out('2'); crashes backend on 7.0.2
Previous Message Lamar Owen 2000-12-12 19:30:01 Re: RPM changes for 7.1.