Re: Hide exposed impl detail of wchar.c

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
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-26 18:24:19
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

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.

regards, tom lane

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2024-01-26 18:28:00 Re: Printing backtrace of postgres processes
Previous Message Bernd Helmle 2024-01-26 18:22:28 Re: [PATCH] Add sortsupport for range types and btree_gist