ONLY in queries by RI triggers
Hi all.
A long time ago in 04b31609b63ce77fb9273193f07cf21b2a7176af ONLY keyword was added to all queries in src/backend/utils/adt/ri_triggers.c. Since that time foreign keys do not work with inheritance trees and it is mentioned in the documentation for all versions since at least 7.3.
I wonder what are the pitfalls of removing ONLY keyword from those queries? I have made such change, it passes all tests and foreign keys for partitioned tables do work, but I suppose that there are lots of places where it could break something.
Thanks in advance.
--
May the force be with you…
https://simply.name
On 2015-04-17 17:35:16 +0300, Vladimir Borodin wrote:
A long time ago in 04b31609b63ce77fb9273193f07cf21b2a7176af ONLY
keyword was added to all queries in
src/backend/utils/adt/ri_triggers.c. Since that time foreign keys do
not work with inheritance trees and it is mentioned in the
documentation for all versions since at least 7.3.I wonder what are the pitfalls of removing ONLY keyword from those
queries? I have made such change, it passes all tests and foreign keys
for partitioned tables do work, but I suppose that there are lots of
places where it could break something.
Unique keys don't work across partitions and they fk triggers rely on
one side being unique...
Greetings,
Andres Freund
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers