Rushabh Lathia wrote: > It might happen that SetVariable() can be called from other places in > future, > so its good to have all the set variable related checks inside > SetVariable().
There's already another way to skip the \set check: select 'on' as "AUTOCOMMIT" \gset But there's a function in startup.c which might be the ideal location for the check, as it looks like the one and only place where the autocommit flag actually changes: static void autocommit_hook(const char *newval) { pset.autocommit = ParseVariableBool(newval, "AUTOCOMMIT"); } Best regards, -- Daniel Vérité PostgreSQL-powered mailer: http://www.manitou-mail.org Twitter: @DanielVerite -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers