On Mon, Feb 2, 2015 at 10:14 PM, Naresh Soni <jmnaresh@xxxxxxxxx> wrote: > > This is only 1 table in the database which will have such huge data i.e 1 > million data per day . no doubt there are other tables in the database but > the records are limited. >> Can the data be easily partitioned? For example, can you set up child >> tables by month for query and archive efficiency? >> > Don't think so. >> >> What sort of query mix do you anticipate? What portion of inserts, >> updates, selects,...? Lots of data-warehouse type queries? >> > Yes, there will be complex queries as this table will be used for reporting > purpose. In short this table will contain Financial Invoices. >> >> Is the schema fairly simple or are there lots of complex foreign-key >> constraints? > > This table has 1 primary and 15 foreign key constraints. I would tend to question your db design here. This layout is setting off alarms for me. It sounds like a "garbage pail" table where you just chuck a bunch of semi-related material without a proper schema for it. That's a recipe for disaster. -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
