Re: Is a syscache tuple more like an on-disk tuple or a freshly made one?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Chapman Flack <chap(at)anastigmatix(dot)net>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Is a syscache tuple more like an on-disk tuple or a freshly made one?
Date: 2016-04-15 22:47:45
Message-ID: 1618.1460760465@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Chapman Flack <chap(at)anastigmatix(dot)net> writes:
> On 04/15/16 18:13, Tom Lane wrote:
>> You could use heap_copy_tuple_as_datum().

> Thanks, that looks like what the doctor ordered.

> For pre-9.4, would the equivalent be basically
> heap_form_tuple applied to the results of heap_deform_tuple ?

You could do that, or you could do what heap_copy_tuple_as_datum
does, ie copy the tuple and then poke the appropriate header
field values into it.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2016-04-15 23:59:40 Re: Optimization for updating foreign tables in Postgres FDW
Previous Message Chapman Flack 2016-04-15 22:43:28 Re: Is a syscache tuple more like an on-disk tuple or a freshly made one?