pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: jian he <jian.universality@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PG 16 draft release notes ready
Date: Sat, 20 May 2023 20:57:47 -0400
Message-ID: <ZGlsi9WGZLPtTo8E@momjian.us> (raw)
In-Reply-To: <927009.1684630281@sss.pgh.pa.us>
References: <ZGaPa7M3gc2THeDJ@momjian.us>
	<CACJufxEhi4QYwNkKU7nwUt+He1YwSdwt52ZBiiFTqK5TwJ9JTQ@mail.gmail.com>
	<ZGlWMOi0+PeJdQ3r@momjian.us>
	<927009.1684630281@sss.pgh.pa.us>

On Sat, May 20, 2023 at 08:51:21PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > I have added this release note item:
> 
> > 	Add functions pg_input_is_valid() and pg_input_error_message() to check for type conversion errors (Tom Lane)
> 
> pg_input_error_message got renamed to pg_input_error_info later,
> cf b8da37b3a (which maybe should be included in the comment
> for this entry).

Oh, I skipped the original entry so I skipped that one too.  I have
adjusted the release note item and added the commit to the comment:

	<!--
	Author: Tom Lane <tgl@sss.pgh.pa.us>
	2022-12-09 [1939d2628] Add test scaffolding for soft error reporting from input
	Author: Michael Paquier <michael@paquier.xyz>
	2023-02-28 [b8da37b3a] Rework pg_input_error_message(), now renamed pg_input_er
	-->
	
	<listitem>
	<para>
-->	Add functions pg_input_is_valid() and pg_input_error_info() to check for type conversion errors (Tom Lane)
	</para>
	</listitem>

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Only you can decide what is important to you.





view thread (141+ messages)  latest in thread

Message-ID: <ZGlsi9WGZLPtTo8E@momjian.us>
Permalink:  ../ZGlsi9WGZLPtTo8E@momjian.us/
Also on:    postgresql.org/message-id/ZGlsi9WGZLPtTo8E@momjian.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-hackers@postgresql.org
  Cc: bruce@momjian.us, tgl@sss.pgh.pa.us, jian.universality@gmail.com
  Subject: Re: PG 16 draft release notes ready
  In-Reply-To: <ZGlsi9WGZLPtTo8E@momjian.us>
  References: <ZGaPa7M3gc2THeDJ@momjian.us> <CACJufxEhi4QYwNkKU7nwUt+He1YwSdwt52ZBiiFTqK5TwJ9JTQ@mail.gmail.com> <ZGlWMOi0+PeJdQ3r@momjian.us> <927009.1684630281@sss.pgh.pa.us> <ZGlsi9WGZLPtTo8E@momjian.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox