Search Postgresql Archives

Re: [EXT] Re: Accessing composite type elements

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [EXT] Re: Accessing composite type elements
From: Garfield Lewis <garfield.lewis@xxxxxxxxxx>
Date: Thu, 2 Jun 2022 17:05:35 +0000
Accept-language: en-CA, en-US
Cc: "pgsql-general@xxxxxxxxxxxxxx" <pgsql-general@xxxxxxxxxxxxxx>
In-reply-to: <1026409.1654187025@sss.pgh.pa.us>
References: <VI1PR0502MB398150C23E5450CCC30BE666E3DE9@VI1PR0502MB3981.eurprd05.prod.outlook.com> <1026409.1654187025@sss.pgh.pa.us>

> 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…

--

Regards,

Garfield A. Lewis

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: [EXT] Re: Accessing composite type elements
  - From: Merlin Moncure

References:
- Accessing composite type elements
  - From: Garfield Lewis
- Re: Accessing composite type elements
  - From: Tom Lane

Prev by Date: Re: Accessing composite type elements
Next by Date: Re: unoptimized nested loops
Previous by thread: Re: Accessing composite type elements
Next by thread: Re: [EXT] Re: Accessing composite type elements
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux