Hannu Krosing wrote:
> Technically this will probably not extend much beyond modifying function
> printtup_internal in src/backend/access/common/printtup.c
>
> /* ----------------
> * printtup_internal
> * We use a different data prefix, e.g. 'B' instead of 'D' to
> * indicate a tuple in internal (binary) form.
> *
> * This is largely same as printtup,except we don't use the typout func.
> * ----------------
> */
> static void
> printtup_internal(HeapTuple tuple, TupleDesc typeinfo, DestReceiver
> *self)
>
>
> The hard part will be agreeing on the actual data format(s), but this
> can be postponed by having this implementation where people can
> experiment.
>
> After looking at the code again, it seems that we must have already
> solved (most) alignment issues in printtup, so the task is just agreeing
> on types' on-wire representations.
I just can't imagine adding anything like that in a minor release. In
fact, I most would object to adding it in a minor release because we
don't add features in a minor release. Now, if you want it kept because
you may want to work in that area, we can surely do that.
-- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610)
853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill,
Pennsylvania19026