From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(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:28:05 |
Message-ID: | 200012122028.PAA08449@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Added to TODO:
* SELECT cash_out(2) crashes because of opaque
> 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
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-12-12 20:44:09 | Re: constrains of array |
Previous Message | Tom Lane | 2000-12-12 20:25:47 | Re: select cash_out('2'); crashes backend on 7.0.2 |
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Myers | 2000-12-12 20:31:12 | Re: CRC was: Re: beta testing version |
Previous Message | Tom Lane | 2000-12-12 20:25:47 | Re: select cash_out('2'); crashes backend on 7.0.2 |