Received: from localhost.localdomain (postgresql.org [64.49.215.8])
	by localhost (Postfix) with ESMTP id 9BD20477386
	for <pgsql-sql@postgresql.org>; Fri, 21 Jun 2002 17:39:59 -0400 (EDT)
Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250])
	by postgresql.org (Postfix) with ESMTP id 28812477570
	for <pgsql-sql@postgresql.org>; Fri, 21 Jun 2002 16:43:22 -0400 (EDT)
Received: from [216.135.165.74] (account <josh@agliodbs.com>)
	by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.5.9)
	with HTTP id 1552196; Fri, 21 Jun 2002 13:43:22 -0700
From: "Josh Berkus" <josh@agliodbs.com>
Subject: Re: is it easy to change the create sequence algorithm?
To: Kevin Brannen <kevinb@nurseamerica.net>, pgsql-sql@postgresql.org
X-Mailer: CommuniGate Pro Web Mailer v.3.5.9
Date: Fri, 21 Jun 2002 13:43:22 -0700
Message-ID: <web-1552196@davinci.ethosmedia.com>
In-Reply-To: <3D0FCD63.8030505@nurseamerica.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Archive-Number: 200206/307
X-Sequence-Number: 8272

Kevin,

> I see in the docs that when I create a column that is of type SERIAL,
> the engine automatically creates the sequence for me, named
> TABLE_COLUMN_seq.  That's great until the table name + column name
> lengths are > 27 chars, then it starts chopping, and you guessed it,
> I have multiple table/column combinations that don't differ until
> after that length.

This would require hacking the Postgres source code.

Sure you don't wanna just create the sequences manually?

If you're sure, post your question to psql-Hackers to find out where
the SERIAL code is located.

-Josh