pgsql: Fix Assert failure in PushOverrideSearchPath when trying to

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix Assert failure in PushOverrideSearchPath when trying to
Date: 2010-08-13 16:27:11
Message-ID: 20100813162711.AA15C7541D7@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Fix Assert failure in PushOverrideSearchPath when trying to restore a search
path that specifies useTemp, but there is no active temp schema in the
current session. (This can happen if the path was saved during a transaction
that created a temp schema and was later rolled back.) For existing callers
it's sufficient to ignore the useTemp flag in this case, though we might
later want to offer an option to create a fresh temp schema. So far as I can
tell this is just an Assert failure: in a non-assert build, the code would
push a zero onto the new search path, which is useless but not very harmful.
Per bug report from Heikki.

Back-patch to 8.3; prior versions don't have this code.

Modified Files:
--------------
pgsql/src/backend/catalog:
namespace.c (r1.127 -> r1.128)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/namespace.c?r1=1.127&r2=1.128)
pgsql/src/backend/utils/cache:
plancache.c (r1.35 -> r1.36)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/cache/plancache.c?r1=1.35&r2=1.36)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2010-08-13 16:27:18 pgsql: Fix Assert failure in PushOverrideSearchPath when trying to
Previous Message Robert Haas 2010-08-13 15:45:17 pgsql: Make RecordTransactionCommit() respect wal_level.