Re: [HACKERS] Declarative partitioning vs. sql_inheritance
От | David Fetter |
---|---|
Тема | Re: [HACKERS] Declarative partitioning vs. sql_inheritance |
Дата | |
Msg-id | 20161216193441.GA12656@fetter.org обсуждение исходный текст |
Ответ на | Re: [HACKERS] Declarative partitioning vs. sql_inheritance (Robert Haas <robertmhaas@gmail.com>) |
Список | pgsql-hackers |
On Fri, Dec 16, 2016 at 11:05:21AM -0500, Robert Haas wrote: > On Thu, Dec 15, 2016 at 10:40 AM, Dmitry Ivanov <d.ivanov@postgrespro.ru> wrote: > > Hi everyone, > > > > Looks like "sql_inheritance" GUC is affecting partitioned tables: > > > > [breaks literally everything] > > > > I might be wrong, but IMO this should not happen. Queries involving update, > > delete etc on partitioned tables are basically broken. Moreover, there's no > > point in performing such operations on a parent table that's supposed to be > > empty at all times. > > An earlier version of Amit's patches tried to handle this by forcing > sql_inheritance on for partitioned tables, but it wasn't > well-implemented and I don't see the point anyway. Sure, turning > off sql_inheritance off for partitioned tables produces stupid > results. But turning off sql_inheritance for inheritance > hierarchies also produces stupid results. If we were going to do > anything about this, my vote would be to remove sql_inheritance. +1 It occurs to me this probably isn't the only GUC that's basically just a foot gun at this point. Is 10 a good time to sweep and clear them? Best, David. -- David Fetter <david(at)fetter(dot)org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate
В списке pgsql-hackers по дате отправления: