What about the risk of using ALTER SEQUENCE ... START N in a mixed
environment? In the 8.4.x servers it will work as designed but in the 8.3.x
(and below) servers, instead of issuing an error it will CORRUPT the
sequence value without notice. I understand the point of keeping a
(mis)feature when it's harmless or at least not amibiguous, but this is not
the case here. While the 8.4 behavior -- the correct one -- is a mere
configuration of little consequence, the 8.3 (and below) behavior is an
unexpected RESET. I think it's safer to require the people that was using
old versions with the wrong spell to fix their code than put lots of users
of the current version in risk of using a potentially disastrous command --
when executed in previous versions. Should all 8.4.x (and beyond) users be
forced to check server version before issuing this command?
2010/9/1 Alvaro Herrera <alvherre@commandprompt.com>
> Excerpts from Euler Taveira de Oliveira's message of mi=E9 sep 01 10:18:10
> -0400 2010:
> > Tom Lane escreveu:
> > > I'm not inclined to go and retroactively document that these spellings
> > > are possible but deprecated in the old branches. I think that would
> > > just confuse matters even more.
> >
> > Is it worth preventing that sloppy implementation in the old branches?
>
> That risks removing a (mis)feature that people are currently depending on.
>
> --
> =C1lvaro Herrera <alvherre@commandprompt.com>
> The PostgreSQL Company - Command Prompt, Inc.
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
>
--=20
Atenciosamente,
Alexsander da Rosa
Linux User #113925
"Extremismo na defesa da liberdade n=E3o =E9 defeito.
Modera=E7=E3o na busca por justi=E7a n=E3o =E9 virtude."
-- Barry Goldwater
