Re: Hide exposed impl detail of wchar.c

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jubilee Young <workingjubilee(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, andres(at)anarazel(dot)de, johncnaylorls(at)gmail(dot)com
Subject: Re: Hide exposed impl detail of wchar.c
Date: 2024-01-29 18:12:49
Message-ID: 20240129181249.GA3669306@nathanxps13
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Fri, Jan 26, 2024 at 01:24:19PM -0500, Tom Lane wrote:
> Nathan Bossart <nathandbossart(at)gmail(dot)com> writes:
>> I see that I was planning on back-patching this to v16, but since
>> is_valid_ascii() was introduced in v15, I'm wondering if it'd be better to
>> back-patch it there so that is_valid_ascii() lives in the same file for all
>> versions where it exists. Thoughts?
> Yeah, if we're going to back-patch at all, that probably makes sense.


Nathan Bossart
Amazon Web Services:

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2024-01-29 18:21:30 Re: cleanup patches for incremental backup
Previous Message Robert Haas 2024-01-29 17:48:32 Re: Flushing large data immediately in pqcomm