Hibernate, web application and only one sequence for all primary keys

From: rawi <only4com(at)web(dot)de>
To: pgsql-sql(at)postgresql(dot)org
Subject: Hibernate, web application and only one sequence for all primary keys
Date: 2009-09-17 12:47:38
Message-ID: [email protected]
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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.

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Gavin McCullagh 2009-09-17 13:01:30 extracting from epoch values in pgsql
Previous Message Mario Splivalo 2009-09-16 20:19:08 CREATE INDEX on column of type 'point'