| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Berend Tober <btober(at)seaworthysys(dot)com>, pgsql-hackers(at)postgreSQL(dot)org, pgsql-general(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Inherited constraints and search paths (was Re: |
| Date: | 2005-05-20 11:11:43 |
| Message-ID: | 1116587503.3844.296.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Thu, 2005-05-19 at 23:27 -0400, Tom Lane wrote:
> Berend Tober <btober(at)seaworthysys(dot)com> writes:
> > Now what, oh most wise one?
>
> OK, now I finally get the point: you are creating child tables in
> different schemas than their parents live in.
...
> Comments anyone?
Best thing to do is to prevent people from creating child tables in
different schemas. Or at least advise against it.
Doing anything to restrict dropping of inherited constraints seems like
wasted effort and potentially annoying anyhow.
My partitioning efforts will eventually distinguish between inherited
and non-inherited constraints, since the former are fairly useless for
partition elimination. So I can't see a reason to care whether they are
there or not, if the user knows better.
Best Regards, Simon Riggs
| From | Date | Subject | |
|---|---|---|---|
| Next Message | GIROIRE, Nicolas (COFRAMI) | 2005-05-20 11:25:45 | Re: triggers using the correct schema .. |
| Previous Message | Paul Newman | 2005-05-20 11:04:16 | triggers using the correct schema .. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2005-05-20 11:21:02 | Re: Notification when freespaces empty |
| Previous Message | Berend Tober | 2005-05-20 07:49:31 | Re: Inherited constraints and search paths (was Re: Preserving |