Re: Inherited constraints and search paths (was Re: - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Inherited constraints and search paths (was Re:
Date
Msg-id 1116587503.3844.296.camel@localhost.localdomain
Whole thread Raw
In response to Inherited constraints and search paths (was Re: [GENERAL] Preserving data after updates)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Inherited constraints and search paths (was Re: [GENERAL]  (Berend Tober <btober@seaworthysys.com>)
Re: [GENERAL] Inherited constraints and search paths (was Re:  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, 2005-05-19 at 23:27 -0400, Tom Lane wrote:
> Berend Tober <btober@seaworthysys.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




pgsql-hackers by date:

Previous
From: ITAGAKI Takahiro
Date:
Subject: Notification when freespaces empty
Next
From: Simon Riggs
Date:
Subject: Re: Notification when freespaces empty