| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Peter Geoghegan <pg(at)heroku(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Documentation of bt_page_items()'s ctid field |
| Date: | 2015-03-09 22:51:57 |
| Message-ID: | CAMkU=1xJ+wzhtgptricULOLjLDLSmyWcX2vQsPbAjOasWzKfHA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Dec 30, 2014 at 8:59 AM, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com
> wrote:
> On 12/30/2014 04:08 AM, Peter Geoghegan wrote:
>
>> Attached documentation patch describes the purpose of
>> bt_page_items()'s ctid field. This has come up enough times in
>> disaster recovery or testing scenarios that I feel it's worth drawing
>> particular attention to.
>>
>
> How much detail on the b-tree internals do we want to put in the
> pageinspect documentation? I can see that being useful, but should we also
> explain e.g. that the first item on each (non-rightmost) page is the high
> key?
>
How do I know if I am looking at a non-rightmost page?
Thanks,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-03-09 23:03:56 | Re: Rethinking the parameter access hooks for plpgsql's benefit |
| Previous Message | Andres Freund | 2015-03-09 22:51:22 | Re: Question about lazy_space_alloc() / linux over-commit |