From: Samba GUEYE <samba.gueye@intesens.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Jim Nasby <jim@nasby.net>
Cc: Postgre Performance <pgsql-performance@postgresql.org>
Cc: ctw@adverb.ly
Subject: Re: Table partitioning problem
Date: Tue, 15 Mar 2011 11:10:01 +0100
Message-ID: <4D7F3AF9.2030207@intesens.com> (raw)
In-Reply-To: <AANLkTinxQ53kCc+V4XHtWmtHw_utwkbuwFz8qVLPg=Hp@mail.gmail.com>
References: <4D764F04.7020400@intesens.com>
<04931568-A1CA-4B5D-B907-E061713E1B54@nasby.net>
<4D788AE2.7010004@intesens.com>
<AANLkTikxt=JTY+dMq769vGOnTYQRmk2O1hJ0YsD5vKLW@mail.gmail.com>
<4D7E455E.5050908@intesens.com>
<AANLkTinxQ53kCc+V4XHtWmtHw_utwkbuwFz8qVLPg=Hp@mail.gmail.com>
Alright thanks all of you for your answers, but i've got 3 more questions :
1. Why "... partitionning is not a good idea ..." like you said
Robert and Conor "... I grant that it would be better to never
need to do that" ?
2. Is there another way or strategy to deal with very large tables
(over 100 000 000 rows per year in one table) beyond indexing and
partitionning?
3. If you had to quantify a limit of numbers of rows per table in a
single postgresql database server what would you say?
PS: i'm using postgresql since less than 2 month because i thought that
partitioning was a possible solution that doesn't offer me Apache Derby
for my large table problem so if these questions sounds "dummy" for you
this is a postgresql novice talking to you.
Regards
Le 14/03/2011 20:40, Robert Haas a écrit :
> On Mon, Mar 14, 2011 at 12:42 PM, Samba GUEYE<samba.gueye@intesens.com> wrote:
>> Yeah but is there a workaround to force the root table to propagate the
>> foreign key to the partitionned table
>> because right now all foreign keys to partitionned table throws constraints
>> violation and it's a big problem for me
> No. Generally, table partitioning is not a good idea unless you are
> dealing with really large tables, and nearly all of your queries apply
> only to a single partition. Most likely you are better off not using
> table inheritance in the first place if you need this feature.
>
> It would be nice if we had a way to do this for the rare cases where
> it would be useful, but we don't.
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: samba.gueye@intesens.com, robertmhaas@gmail.com, jim@nasby.net, ctw@adverb.ly
Subject: Re: Table partitioning problem
In-Reply-To: <4D7F3AF9.2030207@intesens.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox