From: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
---|---|
To: | Magnus Hagander <mha(at)sollentuna(dot)net> |
Cc: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de>, Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Beta2 Wrap Up ... |
Date: | 2005-09-19 03:47:21 |
Message-ID: | 20050919004649.C1105@ganymede.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, 18 Sep 2005, Magnus Hagander wrote:
>>>> Having spent days, no, weeks deciding on that name on list I do not
>>>> want to see it change this late, especially as we'll now need to go
>>>> and update pgAdmin again!
>>
>> Fortunately, pgAdmin doesn't use that function, but only the
>> basic pg_relation_size(). Phew!
>
> Good for you :-)
>
>
>>> Also, the change to pg_cancel_backend breaks backwards compatibility
>>> with 8.0, which is a whole lot worse than breaking it with
>> 8.1-beta1.
>>
>> Unfortunately, core doesn't see this as backward compatibility break,
>> instead it's regarded as adjustment of a new function.
>> Anything that's not in core isn't worth a single thought....
>
> This function has been in core since 8.0. The other functions were new
> (to core that is, imported from external module), but this one was in
> the main backend already.
Is there a reason the old/new can't be aliaseed to each other, instead of
the old just being removed?
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2005-09-19 05:38:36 | Start translating |
Previous Message | Tom Lane | 2005-09-19 03:34:28 | Re: Does anybody use ORDER BY x USING y? |