On Wed, Jan 25, 2012 at 9:54 AM, panam <pa...@gmx.net> wrote: > What do you mean with "explicit sequence object"? An own sequence for each > table per schema?
This: On Wed, Jan 25, 2012 at 10:23 AM, Merlin Moncure <mmonc...@gmail.com> wrote: > Barring domains, you can just manually apply the default instead of > using a serial type: > > create table foo (gid bigint default nextval('global_seq')); http://www.postgresql.org/docs/9.1/static/sql-createsequence.html When you create a 'serial' column, Postgres creates a sequence and makes the column as 'int' with a default that pulls from the sequence. (Similarly for 'bigserial' and 'bigint'.) If you create the sequence yourself, you get a bit more control over it (eg setting min/max/step), and can name it appropriately. Note the OWNED BY clause (as documented in the above link). That's what I was saying about the sequence being owned by or linked to the creating table. ChrisA -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general