Re: ON CONFLICT DO UPDATE for partitioned tables
От | Robert Haas |
---|---|
Тема | Re: ON CONFLICT DO UPDATE for partitioned tables |
Дата | |
Msg-id | CA+TgmoZCLimjt9zxVG7nsBRWJ9Q5JnrbeFyoZh1WMC8+-x6e=w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: ON CONFLICT DO UPDATE for partitioned tables (Alvaro Herrera <alvherre@alvh.no-ip.org>) |
Ответы |
Re: ON CONFLICT DO UPDATE for partitioned tables
|
Список | pgsql-hackers |
On Thu, Apr 19, 2018 at 1:20 PM, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: > Amit Langote wrote: >> Yeah, I too have wondered in the past what it would take to make >> equalTupDescs() return true for parent and partitions. Maybe we can make >> it work by looking a bit harder than I did then. > > How about simply relaxing the tdtypeid test from equalTupleDescs? I > haven't looked deeply but I think just checking whether or not both are > RECORDOID might be sufficient, for typecache purposes. That strike me as a very scary thing to do. There's code all over the system that may have non-obvious assumptions about the behavior of equalTupleDescs(), and I don't think we can have any confidence that nothing will break unless we do a detailed audit of all that code. > If we just remove the tdtypeid test, check-world passes. That does not reassure me. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: