From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: actualised funcs typmod patch |
Date: | 2009-11-17 19:20:47 |
Message-ID: | 162867790911171120y153c8f6fo248542e6700ed568@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2009/11/17 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
>> 2009/11/17 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>>> There are other issues but these are the ones I think we'd need to
>>> resolve before not after putting in function typmods. It'd be
>>> extremely painful and non-backwards-compatible to change our minds
>>> later about function identity or coercion rules.
>
>> I am sure, so this patch cannot break any current code.
>
> My point is that if we release 8.5 with these semantics (which as far
> as I can tell were not designed, but just fell out of what made for the
> shortest patch) then we'll be stuck with them thereafter.
We could to talk about it now. We are not hurry. But I would to see
some progress in this area in next two months. This patch is simple
and doesn't create any new rules or doesn't change behave. Simply
store explicitly defined typmod and use it. Nothing more. If you
thing, so this is poor or problematic - please, show samples and use
cases.
Best regards
Pavel Stehule
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2009-11-17 19:24:12 | Re: Unpredictable shark slowdown after migrating to 8.4 |
Previous Message | Tom Lane | 2009-11-17 18:54:08 | Re: actualised funcs typmod patch |