On Wed, Sep 14, 2016 at 11:09 AM, Tatsuo Ishii <is...@sraoss.co.jp> wrote: >> As I understand the issue, the main reason is that event triggers >> execute procedures, and those exist in a single database only. If you >> were to create an event trigger in database A, then a user gets created >> in database B, your function would not be invoked, which becomes a >> problem. > > Can't we just create the event trigger in database B as well? We have > been living with similar situation, for example, functions for years. > (a work around would be creating functions in template1. This only > works for freshly created database though).
Just a random thought: wouldn't what you are looking for be more reliable if you use the utility hook and have it loaded via preload_shared_libraries? -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
