Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-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

pgsql-hackers by date

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

pgsql-bugs by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group