Received: from localhost (IDENT:root@hectic-2.jpl.nasa.gov [128.149.68.204]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA35899 for ; Thu, 4 Nov 1999 10:57:11 -0500 (EST) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1]) by localhost (8.8.7/8.8.7) with ESMTP id PAA19230; Thu, 4 Nov 1999 15:53:38 GMT Sender: lockhart@hub.org Message-ID: <3821AC01.ABAE5D89@alumni.caltech.edu> Date: Thu, 04 Nov 1999 15:53:37 +0000 From: Thomas Lockhart X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686) X-Accept-Language: en MIME-Version: 1.0 To: stuart@comodo.net CC: pgsql-interfaces@postgreSQL.org Subject: Re: [INTERFACES] sequences References: <99110211052602.00437@FAETHOR> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > The size of a sequence is 32bit , correct? (im pretty damn sure it is). Is > there any way I can tune this to 64bit, There is an int8 option in postgres as > I use that already.Threre is a skanky way of creating an incremenetd counter > whilst using an int8 but I would rather up the sequence in the code. Anyone got > any ideas where to look? Look in src/backend/parser/gram.y and analyze.c for where sequences (the serial type) is handled. The code actually just embeds the "skanky" technique to hide it from the user. A very first cut might be to make this configurable by defining, say, SERIAL_IS_INT64. Patches accepted ;) - Thomas -- Thomas Lockhart lockhart@alumni.caltech.edu South Pasadena, California