On 12/18/13, 2:45 PM, Andres Freund wrote: > Well, the patch's syntax seems to only allow to directly specify a SQL > query to check - we could iterate over the querytree to gather all > related tables and reject any function we do not understand.
Creating an assertion scans the query tree and attaches constraint triggers to all tables covered by the assertion condition. So it does essentially work the way you say. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
