| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | jtc331(at)gmail(dot)com |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pageinspect: add tuple_data_record() |
| Date: | 2018-10-17 02:05:53 |
| Message-ID: | CAH2-WzmKTt7J56DTuKi=DwnFWE7q6Ka78WW6jVj6pdCUy66J_A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 16, 2018 at 6:39 PM James Coleman <jtc331(at)gmail(dot)com> wrote:
> Summary:
> The new function tuple_data_record() parallels the existing tuple_data_split() function, but instead of returning a bytea array of raw attribute heap values, it returns a row type of the relation being examined.
I've been doing something similar with a modified
btreefuncs.c/bt_page_items() recently. The approach I've taken is
pretty grotty. It would be nice to have a reasonable way of doing
this, for both heap tuples and index tuples. (Relatedly,
bt_page_items() should probably have a bytea "data" field instead of a
text "data" field.)
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-10-17 02:17:20 | Re: pageinspect: add tuple_data_record() |
| Previous Message | James Coleman | 2018-10-17 02:05:28 | Re: pageinspect: add tuple_data_record() |