Re: Beta2 Wrap Up ... - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Beta2 Wrap Up ...
Date
Msg-id 6BCB9D8A16AC4241919521715F4D8BCE6C79A9@algol.sollentuna.se
Whole thread Raw
In response to Beta2 Wrap Up ...  ("Marc G. Fournier" <scrappy@postgresql.org>)
List pgsql-hackers
> >>> 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?

It shuold be possible to do for the changed names - not sure if we want
to.
Can't do it for pg_cancel_backend(), because only the return type has
changed and you acn't overload two functions that differ only in return
type.

//Magnus


pgsql-hackers by date:

Previous
From: Mario Weilguni
Date:
Subject: FW:How to modify a tuple returned by SPI_execute
Next
From: "Magnus Hagander"
Date:
Subject: Re: Beta2 Wrap Up ...