| From: | "Zeugswetter Andreas ADI SD" <Andreas(dot)Zeugswetter(at)s-itsolutions(dot)at> |
|---|---|
| To: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, "Gregory Stark" <stark(at)enterprisedb(dot)com> |
| Cc: | "Markus Schiltknecht" <markus(at)bluegap(dot)ch>, "Florian Weimer" <fweimer(at)bfk(dot)de>, "PostgreSQL-development Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Ordered Append Node |
| Date: | 2007-11-23 13:40:40 |
| Message-ID: | E1539E0ED7043848906A8FF995BDA579029138F5@m0143.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > But that requires a) dealing with the problem of the parent table
which has no
> > constraints and ...
Imho we should provide a mechanism that forces the parent to be empty
and let the planner know.
e.g. a false constraint on parent ONLY.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jens-Wolfhard Schicke | 2007-11-23 15:11:47 | Re: Ordered Append Node |
| Previous Message | Markus Schiltknecht | 2007-11-23 13:21:22 | Re: High Availability, Load Balancing, and Replication Feature Matrix |