Re: [EXT] Re: Accessing composite type elements

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Garfield Lewis <garfield(dot)lewis(at)lzlabs(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: [EXT] Re: Accessing composite type elements
Date: 2022-06-02 23:00:41
Message-ID: CAHyXU0z+7hAJuEhDpokOVDee3mcE-X15jhPCy9_4_vxEMskjtw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Jun 2, 2022 at 12:05 PM Garfield Lewis <garfield(dot)lewis(at)lzlabs(dot)com>
wrote:

> > Binary representations are not too well documented :-(. However,
> > looking at record_send() helps here.
>
> will have a look…
>
>
> > Right, with the additional proviso that -1 "length" indicates a null
> > field value.
>
> Thx, Tom… never thought the null field…
>

take a look at libpqtypes. it's client side extension library to libpq that
implements the binary protocol.

https://github.com/pgagarinov/libpqtypes

merlin

>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andreas Joseph Krogh 2022-06-03 08:19:12 Max sane value for join_collapse_limit?
Previous Message Jeff Janes 2022-06-02 19:44:00 Re: unoptimized nested loops