Re: BUG #5269: postgres backend terminates with SIGSEGV

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: BUG #5269: postgres backend terminates with SIGSEGV
Дата
Msg-id 24024.1263483889@sss.pgh.pa.us
обсуждение исходный текст
Ответ на BUG #5269: postgres backend terminates with SIGSEGV  ("Justin Pitts" <justinpitts@gmail.com>)
Ответы Re: BUG #5269: postgres backend terminates with SIGSEGV  (Justin Pitts <jpitts@bplglobal.net>)
Список pgsql-bugs
Justin Pitts <jpitts@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.

> 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.

            regards, tom lane

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Justin Pitts
Дата:
Сообщение: Re: BUG #5269: postgres backend terminates with SIGSEGV
Следующее
От: Tom Lane
Дата:
Сообщение: Re: BUG #5276: pg_ctl reads data directory on -D instead of postgresql.conf directoryh