Performance implications of creating many, many sequences - Mailing list pgsql-general

From Michael Gardner
Subject Performance implications of creating many, many sequences
Date
Msg-id FB36CB57-548C-4E35-A6EC-E44735C33B3C@gmail.com
Whole thread Raw
Responses Re: Performance implications of creating many, many sequences  (Rob Sargent <robjsargent@gmail.com>)
Re: Performance implications of creating many, many sequences  (Craig Ringer <craig@postnewspapers.com.au>)
List pgsql-general
Consider the following table:

CREATE TABLE invoice (
    account_id integer NOT NULL REFERENCES account,
    invoice_number integer NOT NULL,
    UNIQUE (account_id,invoice_number));

I would like to do the equivalent of making invoice_number a serial type, but on a per-account basis. Would it be a
reasonableapproach to create a separate sequence for each individual account? Are there performance implications I
shouldknow about, given that there will be hundreds of thousands of accounts? Is there another approach I should be
lookingat instead? 

pgsql-general by date:

Previous
From: sunpeng
Date:
Subject: Re: how to get the height of index tree?
Next
From: Rob Sargent
Date:
Subject: Re: Performance implications of creating many, many sequences