| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | David Sauer <davids(at)orfinet(dot)cz>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] current CVS snapshot of pgsql crash ... |
| Date: | 1999-07-07 23:52:12 |
| Message-ID: | 199907072352.TAA16153@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Added to TODO:
* Fix typein/out functions to not be user-callable
> 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
>
>
--
Bruce Momjian | http://www.op.net/~candle
maillist(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 | 1999-07-07 23:52:51 | Re: [HACKERS] Open 6.5 items |
| Previous Message | Hiroshi Inoue | 1999-07-07 23:50:53 | RE: [HACKERS] spinlock freeze again |