| From: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | "Fernando Schapachnik" <fernando(at)mecon(dot)gov(dot)ar> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Is this a bug? (changing sequences in default value) |
| Date: | 2008-05-13 15:26:52 |
| Message-ID: | b42b73150805130826v21cbee04q546b2355e32da555@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, May 13, 2008 at 8:50 AM, Fernando Schapachnik
<fernando(at)mecon(dot)gov(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Wall | 2008-05-13 15:27:47 | Re: pg_standby / WAL archive-restore through system restarts |
| Previous Message | David Fetter | 2008-05-13 15:23:34 | Re: Making sure \timing is on |