2016-11-02 15:57 GMT+01:00 Kevin Grittner <kgri...@gmail.com>: > On Sun, Oct 30, 2016 at 10:35 AM, Kevin Grittner <kgri...@gmail.com> > wrote: > > > SPI support would also > > allow us to consider using set logic for validating foreign keys, > > instead of the one-row-at-a-time approach currently used. > > Just as a proof of concept for this I used the attached test case > to create foreign keys using current techniques versus set-oriented > queries with the transition-tsr code. These probably can be > improved, since this is a "first cut" off the top of my head. > > The delete of about one million rows from a "parent" table with no > matching rows in the "child" table, and no index on referencing > column in the child table, took 24:17.969 using current triggers > and 00:03.262 using the set-based triggers. Yes, that reduces > current run time for that case by 99.78% >
this is great number Pavel > > -- > Kevin Grittner > EDB: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers > >
