Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Partitioned tables and views
- From: "Francisco Reyes" <lists(at)stringsutils(dot)com>
- To: " Mike Gould " <mgould(at)allcoast(dot)net>
- Cc: <pgsql-general(at)postgresql(dot)org>
- Subject: Re: Partitioned tables and views
- Date: Thu, 31 Jul 2008 13:55:53 -0400
- Message-id: <9b24b9a57c4123bffdf78df04c7c03ac@stringsutils.com> <text/plain>
On 12:54 pm 07/31/08 "Mike Gould" <mgould(at)allcoast(dot)net> wrote: > 1. Is the planner/optimizer intelligent enough to know when we are > not doing a query based on location? In short yes. If the DB doesn't see the condition by which your tables are partitioned it will search all the partitions. > 2. How are views handled with partitioned tables? Same as with regular queries. A view is just a conveniently "stored" query. In other words, the plan for the view will be the same plan as the plan for the query that you made the view from.
- References:
- Partitioned tables and views
- From: Mike Gould
- Partitioned tables and views
- Prev by Date: PL/pgSQL equivalent to PQtransactionStatus?
- Next by Date: Re: PL/pgSQL equivalent to PQtransactionStatus?
- Previous by thread: Partitioned tables and views
- Next by thread: PL/pgSQL equivalent to PQtransactionStatus?
- Indexes: