From: | 杨杰 <yonj1e(at)163(dot)com> |
---|---|
To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | user-friendliness improvement of pageinspect |
Date: | 2018-07-10 07:41:06 |
Message-ID: | 52bc017.4d33.1648322feb3.Coremail.yonj1e@163.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
Why does the heap_page_item () of the pageinspect extension not consider providing better user-friendliness?
My test table has the following data, and when I look at the t_data I see data of type bytea instead of a more intuitive type, even the same type as the original table.
# select * from test1;
a | b
---+------
1 | text
(1 row)
# SELECT lp as tuple, t_xmin, t_xmax, t_attrs[1] as a, t_attrs[2] as b FROM heap_page_item_attrs(get_raw_page('test1', 0), 'test1');
tuple | t_xmin | t_xmax | a | b
-------+--------+--------+------------+--------------
1 | 587 | 0 | \x01000000 | \x0b74657874
(1 row)
Similar to this effect:
# SELECT lp as tuple, t_xmin, t_xmax, t_attrs[1] as a, t_attrs[2] as b FROM heap_page_item_attrs(get_raw_page('test1', 0), 'test1');
tuple | t_xmin | t_xmax | a | b
-------+--------+--------+------------+--------------
1 | 587 | 0 | 1 | text
(1 row)
Look forward to the solution.
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2018-07-10 07:59:07 | Re: Non-reserved replication slots and slot advancing |
Previous Message | Andres Freund | 2018-07-10 07:26:30 | Re: Non-reserved replication slots and slot advancing |