Re: Inherited constraints and search paths (was Re:

Поиск
Список
Период
Сортировка
Искать
От
Simon Riggs
Тема
Re: Inherited constraints and search paths (was Re:
Дата
в 08:15:30
Msg-id
1116587503.3844.296.camel@localhost.localdomain
Ответ на
Список
Дерево обсуждения
Re: Inherited constraints and search paths (was Re: Simon Riggs <simon@2ndquadrant.com>
Re: [GENERAL] Inherited constraints and search paths (was Re: Tom Lane <tgl@sss.pgh.pa.us>
Re: [GENERAL] Inherited constraints and search paths Simon Riggs <simon@2ndquadrant.com>
Re: [GENERAL] Inherited constraints and search paths (was Re: Tom Lane <tgl@sss.pgh.pa.us>
Re: [GENERAL] Inherited constraints and search paths (was Bruce Momjian <pgman@candle.pha.pa.us>
Re: Inherited constraints and search paths (was Re: [GENERAL] Berend Tober <btober@seaworthysys.com>
On Thu, 2005-05-19 at 23:27 -0400, Tom Lane wrote:
> Berend Tober  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 по дате отправления
От: ITAGAKI Takahiro
Дата:
От: Simon Riggs
Дата:
FAQ