Re: Inherited constraints and search paths (was Re:
От | Simon Riggs |
---|---|
Тема | Re: Inherited constraints and search paths (was Re: |
Дата | |
Msg-id | 1116587503.3844.296.camel@localhost.localdomain обсуждение исходный текст |
Ответ на | Inherited constraints and search paths (was Re: [GENERAL] Preserving data after updates) (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Inherited constraints and search paths (was Re: [GENERAL]
Re: [GENERAL] Inherited constraints and search paths (was Re: |
Список | 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 по дате отправления: