Matthew Dennis wrote: > The cases about taking a string and sending it via execute don't seem to fit > here for 1) cases where it is impossible to track the dependencies can be > trivially constructed and 2) the very nature of the execute statement makes > it obvious that it I shouldn't expect it to be tracked. Poor Analogy: In C, > if foo calls bar and I remove bar I expect the compiler to tell me. If > elsewhere in my code, I construct a memory address of where I believe bar > should be and execute it I have no expectations for the compiler to tell me > bar was removed.
The analogy is poor, yes. A better analogy is the use of dlopen() on a library. If the library is not present at run time, the compiler will not tell you anything. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
