On Wed, Feb 6, 2013 at 7:26 AM, Miroslav Šimulčík <simulcik.m...@gmail.com> wrote: >> Alternately, you might be able to use a custom GUC from a rather smaller >> PL/PgSQL function. At transaction start, issue: >> >> set_config('myapp.trigger_time', '', 't'); > > > This is problem with using custom GUC - clearing variable at transaction > start. Without clearing it's not sufficient solution (see my response to > Pavel's mail).
I might be confused here, but I think the point is that if you pass "true" as the third argument to set_config, the setting lasts only for the duration of the current transaction, like SET LOCAL. Which I think solves your problem. -- Robert Haas EnterpriseDB: 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