Skip site navigation (1) Skip section navigation (2)

Re: max_files_per_process limit

From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
To: Dilek Küçük <dilekkucuk(at)gmail(dot)com>
Cc: "Achilleas Mantzios" <achill(at)matrix(dot)gatewaynet(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: max_files_per_process limit
Date: 2008-11-11 18:59:58
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
On Tue, Nov 11, 2008 at 5:10 AM, Dilek Küçük <dilekkucuk(at)gmail(dot)com> wrote:
> On Mon, Nov 10, 2008 at 4:51 PM, Achilleas Mantzios
> <achill(at)matrix(dot)gatewaynet(dot)com> wrote:
>> Στις Monday 10 November 2008 16:18:37 ο/η Dilek Küçük έγραψε:
>> > Hi,
>> >
>> > We have a database of about 62000 tables (about 2000 tablespaces) with
>> > an
>> > index on each table. Postgresql version is 8.1.
>> >
>> So you have about 62000 distinct schemata in your db?
>> Imagine that the average enterprise has about 200 tables max,
>> and an average sized country has about 300 such companies,
>> including public sector, with 62000 tables you could blindly model
>> .... the whole activity of a whole country.
>> Is this some kind of replicated data?
>> Whats the story?
> Actually we had 31 distinct tables but this amounted to tens of billions of
> records (streaming data from 2000 sites) per table a year, so we
> horizontally partition each table into 2000 tables. This allowed us to
> discard one of the indexes that we have created and freed us from periodical
> cluster operations which turned out to be infeasible for a system with tight
> querying constraints in terms of time.

Any chance of combining less used tables back together to reduce the
number of them?  I'd also look at using more schemas and fewer
tablespaces.  Just a thought.

In response to

pgsql-admin by date

Next:From: Scott MarloweDate: 2008-11-11 19:12:55
Subject: Re: Ideal way to upgrade to postgres 8.3 with less downtime
Previous:From: NetGravitonDate: 2008-11-11 14:47:36
Subject: Web Application Engineer - Drupal, PHP, CSS, JavaScript, Postgresql

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group