Re: Using a postgres table to maintain unique id?
От | Thomas Swan |
---|---|
Тема | Re: Using a postgres table to maintain unique id? |
Дата | |
Msg-id | 5.0.0.25.0.20001114113001.00aad5f8@sunset.backbone.olemiss.edu обсуждение исходный текст |
Ответ на | Re: Using a postgres table to maintain unique id? (Michael Teter <michael_teter@yahoo.com>) |
Список | pgsql-sql |
At 11/13/2000 06:22 PM -0800, Michael Teter wrote:<br /><blockquote cite="cite" class="cite" type="cite">> Can someoneshow me how to create (and use) an int8<br /> > sequence?<br /><br /> From what I can tell (both from docs anddoing a<br /> describe on sequences in my database), a postgresql<br /> sequence is an int4, not an int8, and thus youare<br /> limited to a max of 2.1 billion values.<br /><br /> If you require an int8 sequence, you'll probably have<br/> to manage your own and just use an int8 column.<br /></blockquote><p> I had originally started using int8 and creatingcustom sequences. However, as mentioned in a previous post, there is an inherent performance penalty in using int8over int4. Tom Lane advised me that the int8 routines are an emulated or synthesized data type. in the test I didon our 7.0.2 server I notice about a 25-30% decrease in performance when using complex joins on tables containing referentialkeys, primary keys all in the int8 data type.<br /><br /> This might be something to think about as well.<br /><br/><br /><br />
В списке pgsql-sql по дате отправления: