Excerpts from Robert Haas's message of mar ene 03 12:24:52 -0300 2012: > I feel like the first thing we should be doing here is some > benchmarking. If we change just the scans in dependency.c and then > try the test case Tom suggested (dropping a schema containing a large > number of functions), we can compare the patched code with master and > get an idea of whether the performance is acceptable. If it is, > changing everything else is a mostly mechanical process that we can > simply grind through. If it's not, I'd rather learn that before we > start grinding.
If there are many call sites, maybe it'd be a good idea to use a semantic patcher tool such as Coccinelle instead of doing it one by one. -- Álvaro Herrera <alvhe...@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers