ALTER SEQUENCE
Changes the definition of a sequence generator.
Synopsis
ALTER SEQUENCE [ IF EXISTS ] <name> OWNER TO <new_owner>
ALTER SEQUENCE [ IF EXISTS ] <name> RENAME TO <new_name>
ALTER SEQUENCE [ IF EXISTS ] <name> SET SCHEMA <new_schema>
ALTER SEQUENCE [ IF EXISTS ] <name> [INCREMENT [ BY ] <increment>]
[MINVALUE <minvalue> | NO MINVALUE]
[MAXVALUE <maxvalue> | NO MAXVALUE]
[START [ WITH ] <start> ]
[RESTART [ [ WITH ] <restart>] ]
[CACHE <cache>] [[ NO ] CYCLE]
[OWNED BY {<table.column> | NONE}]
Description
ALTER SEQUENCE changes the parameters of an existing sequence generator.
Any parameters not specifically set in the ALTER SEQUENCE command retain their prior settings.
You must own the sequence to use ALTER SEQUENCE.
To change a sequence’s schema, you must also have the CREATE privilege on the new schema.
Note that superusers have all these privileges automatically.
To alter the owner, you must be a direct or indirect member of the new owning role, and that role must have the CREATE privilege on the sequence’s schema.
These restrictions enforce that altering the owner does not do anything you could not do by dropping and recreating the sequence.
However, a superuser can alter ownership of any sequence anyway.
Parameters
| Parameter | Description |
|---|---|
name |
The name (optionally schema-qualified) of a sequence to be altered |
IF EXISTS |
Do not throw an error if the sequence does not exist. A notice is issued in this case |
increment |
The |
minvalue |
The |
maxvalue |
The |
start |
The |
restart |
The optional |
new_owner |
The user name of the new owner of the sequence |
cache |
The |
CYCLE |
The optional |
NO CYCLE |
If the optional |
OWNED BY table.column |
The |
new_name |
The new name for the sequence |
new_schema |
The new schema for the sequence |
Notes
To avoid blocking of concurrent transactions that obtain numbers from the same sequence, ALTER SEQUENCE effects on the sequence generation parameters are never rolled back; those changes take effect immediately and are not reversible.
However, the OWNED BY, OWNER TO, RENAME TO, and SET SCHEMA clauses are ordinary catalog updates and can be rolled back.
ALTER SEQUENCE will not immediately affect nextval() results in sessions, other than the current one, that have preallocated (cached) sequence values.
They will use up all cached values prior to noticing the changed sequence generation parameters.
The current session will be affected immediately.
For historical reasons, ALTER TABLE can be used with sequences too; but the only variants of ALTER TABLE that are allowed with sequences are equivalent to the forms shown above.
Examples
Restart a sequence called serial at 105:
ALTER SEQUENCE serial RESTART WITH 105;
Compatibility
ALTER SEQUENCE conforms to the SQL standard, except for the START WITH, OWNED BY, OWNER TO, RENAME TO, and SET SCHEMA clauses, which are Greengage DB extensions.