Re: Is this a bug? (changing sequences in default value) - Mailing list pgsql-general

From Merlin Moncure
Subject Re: Is this a bug? (changing sequences in default value)
Date
Msg-id b42b73150805130826v21cbee04q546b2355e32da555@mail.gmail.com
Whole thread Raw
In response to Re: Is this a bug? (changing sequences in default value)  (Fernando Schapachnik <fernando@mecon.gov.ar>)
Responses Re: Is this a bug? (changing sequences in default value)
List pgsql-general
On Tue, May 13, 2008 at 8:50 AM, Fernando Schapachnik
<fernando@mecon.gov.ar> wrote:
>  > > ALTER SEQUENCE name [ INCREMENT [ BY ] increment ]
>  > >    [ MINVALUE minvalue | NO MINVALUE ] [ MAXVALUE maxvalue | NO
>  > > MAXVALUE ]
>  > >    [ RESTART [ WITH ] start ] [ CACHE cache ] [ [ NO ] CYCLE ]
>  >
>  > oop, you are using 8.1 :-).  This was added in a later version.  drop
>  > sequence ... cascade should probably work.  you can try it out in a
>  > transaction to be sure.
>
>  Thanks for your help, but cascade doesn't make a difference.

What do you mean? PostgreSQL 8.1 has 'drop sequence cascade':
http://www.postgresql.org/docs/8.1/interactive/sql-dropsequence.html

If this isn't working, can you paste the text of the error message?

merlin

pgsql-general by date:

Previous
From: David Fetter
Date:
Subject: Re: Making sure \timing is on
Next
From: David Wall
Date:
Subject: Re: pg_standby / WAL archive-restore through system restarts