> -Original Message-
> From: sandeep prakash dhumale [mailto:sandy9...@rediffmail.com]
> Sent: Tuesday, September 28, 2010 6:32 AM
> To: pgsql-general@postgresql.org
> Subject: Scaling PostgreSQL-9
>
> Hello All,
>
> Need some help in scaling PostgreSQL:
>
> I have a table with 400M
On Tue, Sep 28, 2010 at 8:56 AM, Sandy wrote:
> Table has mobile number,status and expiry date. I can not partition on
> expiry date as all SELECT's are on mobile number.
>
Then partition on the mobile number. If your updates and queries are all
tied to that, then it is the ideal candidate.
Yo
On Tue, 28 Sep 2010 17:45:16 +0530 wrote
>On Tue, Sep 28, 2010 at 6:31 AM, sandeep prakash dhumale wrote:
I have a table with 400M records with 5 int columns having index only on 1
column.
How is your data used? Is the update done by the primary key? Are the queries
segmented in some way
On Tue, Sep 28, 2010 at 6:31 AM, sandeep prakash dhumale <
sandy9...@rediffmail.com> wrote:
> I have a table with 400M records with 5 int columns having index only on 1
> column.
>
How is your data used? Is the update done by the primary key? Are the
queries segmented in some way that may divid
Hello All,
Need some help in scaling PostgreSQL:
I have a table with 400M records with 5 int columns having index only on 1
column.
Rows are updated by a perl script which takes 10k numbers in one transactions
and fires single single update in a loop on database keeping track of the
result re
