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: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Open 7.1 items |
Date: | 2001-01-25 11:20:11 |
Message-ID: | 27041.980421611@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Here are my open 7.1 items. Thanks for shrinking the list so far.
> SELECT cash_out(1) crashes all backends
This isn't a "must fix for 7.1", any more than it was for 7.0, 6.5,
or any other release back to the beginning of time. It's always been
possible to crash the backend by passing an incompatible argument to
a type input or output function. The type-checking system cannot
detect the error because these functions are (mostly) declared to
take "any" input type (zero entry in proargtypes[]).
The only clean way to fix this is to declare I/O functions honestly.
That will require (a) a type-system representation for "C string"
and (b) a solution to the circularity issue for user-defined types.
If the I/O functions have to be declared first, how can they refer
to the type?
Quite aside from the time involved, this will require an initdb.
It's a bit late in the cycle for that.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Frank Joerdens | 2001-01-25 12:35:05 | Re: beta3 Solaris 7 (SPARC) port report [ Was: Looking for . . . ] |
Previous Message | Peter T Mount | 2001-01-25 10:06:16 | Re: Open 7.1 items |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter T Mount | 2001-01-25 13:21:01 | Re: Re: [BUGS] JDBC PreparedStatement.setMaxRows() affects other objects instantiated from this class and it's parent class |
Previous Message | Ramachandra K.B.S | 2001-01-25 10:29:52 | RE: Re: Postgresql JDBC driver - Support for Scrollable Re sult Sets |