Re: [HACKERS] [PATCH] pageinspect function to decode infomasks
| От | Craig Ringer |
|---|---|
| Тема | Re: [HACKERS] [PATCH] pageinspect function to decode infomasks |
| Дата | |
| Msg-id | CAMsr+YERdL-KsgaTs=y42BQoram67CEOth7HW=qmWG55hJHEJA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] [PATCH] pageinspect function to decode infomasks (Ashutosh Sharma <ashu.coek88@gmail.com>) |
| Ответы |
Re: [HACKERS] [PATCH] pageinspect function to decode infomasks
|
| Список | pgsql-hackers |
On 14 September 2017 at 19:57, Ashutosh Sharma <ashu.coek88@gmail.com> wrote:
Are you planning to work on the review comments from Robert, Moon
Insung and supply the new patch. I just had a quick glance into this
mail thread (after a long time) and could understand Robert's concern
till some extent. I think, he is trying to say that if a tuple is
frozen (committed|invalid) then it shouldn't be shown as COMMITTED and
INVALID together in fact it should just be displayed as FROZEN tuple.
Yes, I'd like to, and should have time for it in this CF.
My plan is to emit raw flags by default, so FROZEN would't be shown at all, only COMMITTED|INVALID. If the bool to decode combined flags is set, then it'll show things like FROZEN, and hide COMMITTED|INVALID. Similar for other combos.
В списке pgsql-hackers по дате отправления: