| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Oliver Elphick <olly(at)lfix(dot)co(dot)uk>, Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: OPAQUE and 7.2-7.3 upgrade |
| Date: | 2002-09-13 04:09:06 |
| Message-ID: | 15130.1031890146@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Philip Warner <pjw(at)rhyme(dot)com(dot)au> writes:
> At 11:27 PM 12/09/2002 -0400, Tom Lane wrote:
>> You mean hardwire the names "plpgsql_language_handler", etc, as being
>> ones that should return such-and-such instead of OPAQUE?
> No; I actually mean modifying the function definition macros
> (PG_FUNCTION_INFO etc) to allow function definitions to (optionally)
> include return type (at least for builtin types with fixed IDs) - they
> already define the invocation method etc, so it does not seem a big stretch
> to add a return type ID.
That cannot work for user-defined functions, wherein the datatype OID is
not frozen at the time the code is compiled. In any case, it surely
does not help for our current problem, which is forward-compatibility
of dumps from 7.2 databases...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-09-13 04:11:59 | Re: OPAQUE and 7.2-7.3 upgrade |
| Previous Message | Yury Bokhoncovich | 2002-09-13 04:08:48 | btree page merging |