On Jan 14, 2010, at 10:44 AM, Tom Lane wrote: > Justin Pitts <jpi...@bplglobal.net> writes: >> On Jan 14, 2010, at 10:16 AM, Tom Lane wrote: >>> The 100 temp table creations probably will do that just fine. > >> Is there a way to verify this? > > You could add an elog(LOG, "message") into ResetPlanCache so you could > tell when it had been called. >
Done. Sometimes I see it, sometimes not. >> I don't follow. Are you suggesting I begin another transaction on connection >> 1 with a read, and that >> would provoke the crash? > > Yes. The rollback only sets the stage for the next transaction to try > to use a snapshot that isn't there anymore. > Oh, duh. A read from the same session that rolled-back. That didn't get it working (failing?) however. Running concurrent instances of this test reliably provokes the crash on un-patched 8.4.2. They do not provoke a crash with the patch. That's what i was looking for. Thanks! > regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
