Re: Performance with very large tables

From: "Shoaib Mir" <shoaibmir(at)gmail(dot)com>
To: "Richard Huxton" <dev(at)archonet(dot)com>
Cc: "Jan van der Weijde" <Jan(dot)van(dot)der(dot)Weijde(at)attachmate(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Performance with very large tables
Date: 2007-01-15 11:37:25
Message-ID: bf54be870701150337t3fd17329i43d9d738ccfa647f@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Oh yes, need to have a condition first for which you have partitioned
tables. Only in that case it will work with partitions.

---------------
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)

On 1/15/07, Richard Huxton <dev(at)archonet(dot)com> wrote:
>
> Shoaib Mir wrote:
> > You can also opt for partitioning the tables and this way select will
> only
> > get the data from the required partition.
>
> Not in the case of SELECT * FROM <table> though. Unless you access the
> specific partitioned table.
>
> > On 1/15/07, Richard Huxton <dev(at)archonet(dot)com> wrote:
> >>
> >> Jan van der Weijde wrote:
> >> > Hello all,
> >> >
> >> > one of our customers is using PostgreSQL with tables containing
> >> millions
> >> > of records. A simple 'SELECT * FROM <table>' takes way too much
> >> time in
> >> > that case, so we have advised him to use the LIMIT and OFFSET
> clauses.
>
> --
> Richard Huxton
> Archonet Ltd
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Alban Hertroys 2007-01-15 11:49:03 Re: Performance with very large tables
Previous Message Richard Huxton 2007-01-15 11:29:34 Re: Performance with very large tables