Re: pgsql: Refactor pg_get_line() to expose an alternative StringInfo-based - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Refactor pg_get_line() to expose an alternative StringInfo-based
Date
Msg-id 1700043.1599501520@sss.pgh.pa.us
Whole thread Raw
In response to pgsql: Refactor pg_get_line() to expose an alternative StringInfo-based  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> On 2020-Sep-07, Tom Lane wrote:
>> If there were something to be on the warpath about, it's that initdb
>> is pulling in such an obviously backend-only header as that.  I wonder
>> if we should refactor to fix that.

> Hmm, if we wanted to clean things up I think we should look at what
> other things from xlog_internal.h are being used by other frontend
> programs;

Yeah, I was thinking along the same lines, but hadn't done the legwork
to see what else is needed by frontend code.

            regards, tom lane



pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Refactor pg_get_line() to expose an alternative StringInfo-based
Next
From: Tom Lane
Date:
Subject: pgsql: Clarify comments in enforce_generic_type_consistency().