Hibernate, web application and only one sequence for all primary keys - Mailing list pgsql-sql

From rawi
Subject Hibernate, web application and only one sequence for all primary keys
Date
Msg-id 25490498.post@talk.nabble.com
Whole thread Raw
Responses Re: Hibernate, web application and only one sequence for all primary keys  (rawi <only4com@web.de>)
Re: Hibernate, web application and only one sequence for all primary keys  (Leo Mannhart <leo.mannhart@beecom.ch>)
Re: Hibernate, web application and only one sequence for all primary keys  (Tom Lane <tgl@sss.pgh.pa.us>)
Thank you all for your help...  (rawi <only4com@web.de>)
Re: Hibernate, web application and only one sequence for all primary keys  (Lew <noone@lwsc.ehost-services.com>)
List pgsql-sql
Hello!

The subject says it...

Grails/Hibernate wishes per default one sequence for all tables-PKs and all
PKs as BigInt.

What would you think about a database with some tens of tables and
incidentally low to moderate insert concurrency spread in about the half of
the tables from at most 10 concurrent users with some 10-20 inserts each?

And (for the eventuality of an unexpected need to scale up in the future -
e.g. integration of multiple databases), from about which size would you
expect performance penalties due to the sole sequence and the BigInt-PKs?

I first intend to deploy it on an Intel Pentium 2 Duo (2.5-2.8GHz) with 3 GB
RAM and SATA hard disk under Ubuntu Server.

Thank you very much in advance!
Regards
Rawi
-- 
View this message in context:
http://www.nabble.com/Hibernate%2C-web-application-and-only-one-sequence-for-all-primary-keys-tp25490498p25490498.html
Sent from the PostgreSQL - sql mailing list archive at Nabble.com.



pgsql-sql by date:

Previous
From: std pik
Date:
Subject: hardware information
Next
From: rawi
Date:
Subject: Re: Hibernate, web application and only one sequence for all primary keys