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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Refactor pg_get_line() to expose an alternative StringInfo-based
Date: 2020-09-07 17:58:40
Message-ID: 1700043.1599501520@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Alvaro Herrera <alvherre(at)2ndquadrant(dot)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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2020-09-07 18:52:42 pgsql: Clarify comments in enforce_generic_type_consistency().
Previous Message Alvaro Herrera 2020-09-07 17:34:38 Re: pgsql: Refactor pg_get_line() to expose an alternative StringInfo-based