| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Mikael Carneholm <Mikael(dot)Carneholm(at)WirelessCar(dot)com> |
| Cc: | "'Pgsql-General (E-mail)" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Partitioning attempts |
| Date: | 2005-10-31 20:43:30 |
| Message-ID: | 1130791410.8300.1515.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 2005-10-31 at 21:02 +0100, Mikael Carneholm wrote:
> So far so good. Now, the part where it fails to be useful (performance wise) is when you want to make sure a select query only scans the relevant partition(s), as it's not possible to create a conditional SELECT rule using an INSTEAD select ... from ONLY ..., i.e:
There is no need to do this.
Try doing a select against mastertab and you will see that it only
selects from the correct partitions. Look at constraint_exclusion
parameter, which needs to be set on for this to work.
> Also, we would need UPDATE and DELETE rules, but these are tricky as an update may involve both inserting and deleting rows (if the row belongs to another child table after the update).
Not implemented in 8.1
Best Regards, Simon Riggs
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2005-10-31 20:50:31 | Re: Starting PostgreSQL 8.0.4 with more memory [FreeBSD |
| Previous Message | Daniel Verite | 2005-10-31 20:34:40 | Re: Re: [GENERAL] Sorting problems with SELECT * FROM |