Re: Patch: show relation and tuple infos of a lock to acquire

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: Patch: show relation and tuple infos of a lock to acquire
Дата
Msg-id CA+TgmoYSD4k60-_shHcOH_NWDju8Ayk+F3UqHtAWAq7WN6vMcQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Patch: show relation and tuple infos of a lock to acquire  (Amit Kapila <amit.kapila16@gmail.com>)
Ответы Re: Patch: show relation and tuple infos of a lock to acquire  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: Patch: show relation and tuple infos of a lock to acquire  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On Tue, Mar 18, 2014 at 12:00 AM, Amit Kapila <amit.kapila16@gmail.com> wrote:
>> Therefore I think the only case worth considering here is when
>> database/relation/TID are all defined.  The other cases where there is
>> partial information are dead code; and the case where there is nothing
>> defined (such as the one in SnapBuildFindSnapshot) is already handled by
>> simply not setting up a context at all.
>
> Right. So I think we should just keep one version of message.

Well, if we're back to one version of the message, and I'm glad we
are, can we go back to saying:

CONTEXT:  while updating tuple (0,2) in relation "public"."foo" of
database "postgres"

Instead of:

CONTEXT:  while operating on tuple (0,2) in relation "public"."foo" of
database "postgres": updating tuple

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



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

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: Patch: show relation and tuple infos of a lock to acquire
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Portability issues in shm_mq