Re: Patch: plan invalidation vs stored procedures
| От | Asko Oja |
|---|---|
| Тема | Re: Patch: plan invalidation vs stored procedures |
| Дата | |
| Msg-id | ecd779860808191042p5a3a7714wc2e52241ad3211ef@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Patch: plan invalidation vs stored procedures (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-hackers |
Polite answers lead to polite discussions. Caling other people names lead to flame wars.
It's perfectly ok for Skype to keep our own build of 8.3 with given patch and make it available for whoever might want it. At least now there is almost good enough description why the patch was needed althou it would have been more pleasant if the discussion had been constructive.
We didn't keep close enough watch on the list when 8.3 plan invalidation was discussed and it came as bad surprise to us that some parts important to us were left out.
By the way it's real nice what you are doing with in and exists improvements. Thanks.
regards
Asko
It's perfectly ok for Skype to keep our own build of 8.3 with given patch and make it available for whoever might want it. At least now there is almost good enough description why the patch was needed althou it would have been more pleasant if the discussion had been constructive.
We didn't keep close enough watch on the list when 8.3 plan invalidation was discussed and it came as bad surprise to us that some parts important to us were left out.
By the way it's real nice what you are doing with in and exists improvements. Thanks.
regards
Asko
On Tue, Aug 19, 2008 at 8:06 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Dimitri Fontaine <dfontaine@hi-media.com> writes:> Another thing I do not understand well is how people are expected to work inI could understand this level of complaining if this were a new problem
> 8.3 with a function based API, without hitting Skype problems.
that'd appeared in 8.3. But *every PG version that we've ever released*
behaves the same way with respect to function drop/recreate. If the
Skype folk have developed a way of working that is guaranteed not to
work with any released version, one has to wonder what they were
thinking.
If you need to DROP rather than CREATE OR REPLACE functions, then 8.3
doesn't make things better for you than prior releases did, but it
does't make them worse either. Making things better for that case is
unequivocally a new feature. And it's rather a corner case at that,
else there would have been enough prior complaints to put it on the
radar screen for 8.3.
What we've got at this point is a submitted patch for a new feature
that hasn't even been accepted into HEAD yet. Lobbying to get it
back-patched is entirely inappropriate IMHO.
regards, tom lane
--Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: