user-friendliness improvement of pageinspect
От
杨杰
Тема
user-friendliness improvement of pageinspect
Дата
Msg-id
52bc017.4d33.1648322feb3.Coremail.yonj1e@163.com
Список
Дерево обсуждения
user-friendliness improvement of pageinspect 杨杰 <yonj1e@163.com>
Re: user-friendliness improvement of pageinspect Peter Geoghegan <pg@bowt.ie>
回复： user-friendliness improvement of pageinspect "Yang Jie" <yonj1e@163.com>
Re: user-friendliness improvement of pageinspect Peter Geoghegan <pg@bowt.ie>
Re: user-friendliness improvement of pageinspect "Yang Jie" <yonj1e@163.com>
Re: user-friendliness improvement of pageinspect Peter Geoghegan <pg@bowt.ie>
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.
В списке pgsql-hackers по дате отправления
