| From: | "Yang Jie" <yonj1e(at)163(dot)com> |
|---|---|
| To: | "Peter Geoghegan" <pg(at)bowt(dot)ie> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | 回复: user-friendliness improvement of pageinspect |
| Date: | 2018-07-11 01:44:35 |
| Message-ID: | cdc759a.23ce.1648702f53c.Coremail.yonj1e@163.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thank you for your answer.
my question is not split the data into individual attributes.
I want to see the data in the table, but I don't want to be a bytea type.
在2018年7月11日 02:48,Peter Geoghegan<pg(at)bowt(dot)ie> 写道:
On Tue, Jul 10, 2018 at 12:41 AM, 杨杰 <yonj1e(at)163(dot)com> wrote:
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.
tuple_data_split() can do this (split the data into individual
attributes). If you want a friendlier, more visual way of getting this
information, then you may find pg_hexedit helpful:
https://github.com/petergeoghegan/pg_hexedit
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2018-07-11 01:47:21 | Re: Speeding up INSERTs and UPDATEs to partitioned tables |
| Previous Message | Thomas Munro | 2018-07-11 01:16:31 | Re: Excessive PostmasterIsAlive calls slow down WAL redo |