From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
Cc: | Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Bundle of patches |
Date: | 2006-12-04 19:04:26 |
Message-ID: | 19734.1165259066@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Teodor Sigaev <teodor(at)sigaev(dot)ru> writes:
> 1) Typmod for user-defined types
> http://www.sigaev.ru/misc/user_defined_typmod-0.7.gz
> Patch is based on ideas from
> http://archives.postgresql.org/pgsql-hackers/2004-06/msg00932.php
> http://archives.postgresql.org/pgsql-hackers/2005-08/msg01007.php
This one seems generally workable, but I really dislike the approach
that's been used for passing typmod arguments to the typmod_in function.
Representing them with an "internal" parameter means it'll be forever
impossible to write typmod functions in anything but C, which seems an
ugly restriction. Perhaps an array of int4 would be better? How much
flexibility do we really want to provide for typmod arguments? Allowing
full "expr_list" in the grammar seems less than sane, considering the
result is still going to have to pack into 32 bits.
The patch needs more cleanup before applying, too, eg make comments
match code, get rid of unused keywords added to gram.y.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2006-12-04 19:07:50 | old synchronized scan patch |
Previous Message | Bruce Momjian | 2006-12-04 19:04:19 | Postgres95 archives in mbox format |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-12-04 19:26:28 | Re: [HACKERS] Bundle of patches |
Previous Message | Teodor Sigaev | 2006-12-04 18:46:15 | Re: Bundle of patches |