Re: Deduplicate logicalrep_read_tuple() - Mailing list pgsql-hackers

From Bharath Rupireddy
Subject Re: Deduplicate logicalrep_read_tuple()
Date
Msg-id CALj2ACV1N+_HvTVxWmCe5qBd3mUR0rWr-Q_7mBLipdz62O19NQ@mail.gmail.com
Whole thread Raw
In response to Re: Deduplicate logicalrep_read_tuple()  (Peter Smith <smithpb2250@gmail.com>)
Responses Re: Deduplicate logicalrep_read_tuple()
List pgsql-hackers
On Thu, Jan 19, 2023 at 8:36 AM Peter Smith <smithpb2250@gmail.com> wrote:
>
> On Wed, Jan 18, 2023 at 6:26 PM Bharath Rupireddy
> <bharath.rupireddyforpostgres@gmail.com> wrote:
> >
> > Hi,
> >
> > logicalrep_read_tuple() duplicates code for LOGICALREP_COLUMN_TEXT and
> > LOGICALREP_COLUMN_BINARY introduced by commit 9de77b5. While it
> > doesn't hurt anyone, deduplication makes code a bit leaner by 57 bytes
> > [1]. I've attached a patch for $SUBJECT.
> >
> > Thoughts?
> >
>
> The code looks the same but there is a subtle comment difference where
> previously only LOGICALREP_COLUMN_BINARY case said:
>  /* not strictly necessary but per StringInfo practice */
>
> So if you de-duplicate the code then should that comment be modified to say
> /* not strictly necessary for LOGICALREP_COLUMN_BINARY but per
> StringInfo practice */

Thanks. Done so in the attached v2.

--
Bharath Rupireddy
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

Attachment

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: min/max aggregation for jsonb
Next
From: Alvaro Herrera
Date:
Subject: Re: cataloguing NOT NULL constraints