2009/12/17 David Fetter <david@xxxxxxxxxx>: >> You really think that calling and running a trigger function for every >> line is the best solution? > > Yes. The trigger function is choosing from a small subset of the > tables, or you know which tables exactly the rows are going into and > insert them there. So I understand that when a table has multiple RULEs, the planner just browse all of them to check the one(s) that will apply. What I have in mind is a "side table" with some bookkeeping data to be used by the trigger function to select the actual table to be used. Do you think this is faster than RULEs? Is there any performance study for the trigger-based implementation? > Oh, and please do trim, and don't top-post. I've fix this in this > post. Sorry! :-) -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
