On Thu, Jun 02, 2005 at 12:58:33PM +0300, Kaloyan Iliev Iliev wrote: > Hi, > > I suppose the paralel work will be a problem if you are using one > sequence for all tables. If you insert a large amount of rows in > different tables there will be great slowdown because your sequence is > the bottle neck of your database. All the inserts must read from it one > by one. If you have many sequences (one for each table PK) every insert > in a different table will use different sequence and this will improve > performance. I don't know about this. Sequences are designed to be very efficient, they don't rollback and can be cached by backends. In several of the databases I setup, I sometimes arranged for sequences to start at different points so when you setup a foreign key there was no chance you linked it to the wrong table. This especially in cases where there might be confusion about which table links where. Using one serial for everything does this even better. As for performance, I think disk I/O is going to be an issue before getting sequence numbers will be... -- Martijn van Oosterhout <kleptog@xxxxxxxxx> http://svana.org/kleptog/ > Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a > tool for doing 5% of the work and then sitting around waiting for someone > else to do the other 95% so you can sue them.
Attachment:
pgpafpbq6MyRQ.pgp
Description: PGP signature
