Re: pgsql: Prevent "snapshot too old" from trying to return pruned TOAST tu

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: pgsql: Prevent "snapshot too old" from trying to return pruned TOAST tu
Дата
Msg-id CA+TgmobB_gM57=aUfqqbkc4g+K3_pNAX+StJSn0nXZLH9LROjg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: pgsql: Prevent "snapshot too old" from trying to return pruned TOAST tu  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-committers
Дерево обсуждения 
On Thu, Aug 4, 2016 at 7:23 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <rhaas@postgresql.org> writes:
>> Prevent "snapshot too old" from trying to return pruned TOAST tuples.
>
> Looks like this patch broke the build on castoroides.  Recommend
> changing InitToastSnapshot into a macro.  (There's a reason why
> InitDirtySnapshot is a macro.)

What is the reason?  We refuse to separate frontend and backend
headers in any sort of principled way?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: pgsql: Prevent "snapshot too old" from trying to return pruned TOAST tu
Следующее
От: Andres Freund
Дата:
Сообщение: pgsql: Fix hard to hit race condition in heapam's tuple locking code.