Postgres Pro
Downloads
Home   >   mailing lists

Re: machine-readable explain output - Mailing list pgsql-hackers

From Tom Lane
Subject Re: machine-readable explain output
Date
Msg-id 14381.1245073907@sss.pgh.pa.us
Whole thread Raw
In response to Re: machine-readable explain output  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: machine-readable explain output  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Tree view 
Robert Haas <robertmhaas@gmail.com> writes:
> Hmm... on further review, I'm thinking this is still a bit wastful,
> because we don't really need (I think) to call
> TupleDescGetAttInMetadata from begin_tup_output_tupdesc.  But I'm not
> sure what the best way is to avoid that.  Any thoughts?

Er, just don't do it?  We shouldn't need it if the function is doing
heap_form_tuple directly.
        regards, tom lane

pgsql-hackers by date:

Previous
From: Gurjeet Singh
Date:
Subject: Re: char() overhead on read-only workloads not so insignifcant as the docs claim it is...
Next
From: Tom Lane
Date:
Subject: Re: Should mdxxx functions(e.g. mdread, mdwrite, mdsync etc) PANIC instead of ERROR when I/O failed?