pgsql: Fix an old corner-case bug in set_config_option: push_old_value - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Fix an old corner-case bug in set_config_option: push_old_value
Date
Msg-id 20080526185430.12BAE754C54@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Fix an old corner-case bug in set_config_option: push_old_value has to be
called before, not after, calling the assign_hook if any.  This is because
push_old_value might fail (due to palloc out-of-memory), and in that case
there would be no stack entry to tell transaction abort to undo the GUC
assignment.  Of course the actual assignment to the GUC variable hasn't
happened yet --- but the assign_hook might have altered subsidiary state.
Without a stack entry we won't call it again to make it undo such actions.
So this is necessary to make the world safe for assign_hooks with side
effects.  Per a discussion a couple weeks ago with Magnus.

Back-patch to 8.0.  7.x did not have the problem because it did not have
allocatable stacks of GUC values.

Modified Files:
--------------
    pgsql/src/backend/utils/misc:
        guc.c (r1.454 -> r1.455)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/guc.c?r1=1.454&r2=1.455)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Adjust timestamp regression tests to prevent two low-probability
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Fix an old corner-case bug in set_config_option: push_old_value