| From: | Chapman Flack <chap(at)anastigmatix(dot)net> | 
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> | 
| Subject: | Is a syscache tuple more like an on-disk tuple or a freshly made one? | 
| Date: | 2016-04-15 21:55:10 | 
| Message-ID: | 5711633E.20503@anastigmatix.net | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
Please bear with a neophyte question ...
I am tempted to apply HeapTupleGetDatum to a tuple retrieved from
the syscache (as I already have code for processing a tuple presented
as a Datum).
But I see a comment on HeapTupleHeaderGetDatum: "This must *not* get
applied to an on-disk tuple; the tuple should be freshly made by
heap_form_tuple or some wrapper ..."
... and here I confess I'm unsure whether a tuple retrieved from
the syscache is more like an on-disk one, or a freshly-made one,
for purposes of the warning in that comment.
Is there a conventional proper way to pass a tuple retrieved from
syscache to code that accepts a tuple as a Datum? Or is there some
fundamental reason a smart person wouldn't do that?
Thanks,
-Chap
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2016-04-15 22:03:01 | Re: Is a syscache tuple more like an on-disk tuple or a freshly made one? | 
| Previous Message | Stephen Frost | 2016-04-15 21:11:43 | Re: [COMMITTERS] pgsql: Add new catalog called pg_init_privs |