Re: Reducing output size of nodeToString - Mailing list pgsql-hackers

From Matthias van de Meent
Subject Re: Reducing output size of nodeToString
Date
Msg-id CAEze2WgKVdmMLAGga8Gfh7DsvuJPxiqPvYH8fS0Px8f3w5g64g@mail.gmail.com
Whole thread Raw
In response to Re: Reducing output size of nodeToString  (Matthias van de Meent <boekewurm+postgres@gmail.com>)
Responses Re: Reducing output size of nodeToString
List pgsql-hackers
On Thu, 22 Feb 2024 at 13:37, Matthias van de Meent
<boekewurm+postgres@gmail.com> wrote:
>
> On Mon, 19 Feb 2024 at 14:19, Matthias van de Meent
> <boekewurm+postgres@gmail.com> wrote:
> > Attached the updated version of the patch on top of 5497daf3, which
> > incorporates this last round of feedback.
>
> Now attached rebased on top of 93db6cbd to fix conflicts with fbc93b8b
> and an issue in the previous patchset: I attached one too many v3-0001
> from a previous patch I worked on.

... and now with a fix for not overwriting newly deserialized location
attributes with -1, which breaks test output for
READ_WRITE_PARSE_PLAN_TREES installations. Again, no other significant
changes since the patch of last Monday.

Sorry for the noise,

-Matthias

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Test to dump and restore objects left behind by regression
Next
From: Matthias van de Meent
Date:
Subject: Re: btree: downlink right separator/HIKEY optimization