Date: Wed, 13 Aug 2025 10:17:55 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@lists.postgresql.org>
Subject: Re: PG 18 release notes draft committed
Message-ID: <aJyek0Fnm5v6vvmA@momjian.us>
References: <aBQxop9YxQDad8-W@momjian.us>
 <CAA4eK1KN-SYDARdQpME1HGJFsySxF-BmbCvAWct9dUYpBTwqBg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CAA4eK1KN-SYDARdQpME1HGJFsySxF-BmbCvAWct9dUYpBTwqBg@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/aJyek0Fnm5v6vvmA%40momjian.us>
Precedence: bulk

On Wed, Aug 13, 2025 at 11:38:33AM +0530, Amit Kapila wrote:
> On Fri, May 2, 2025 at 8:14 AM Bruce Momjian <bruce@momjian.us> wrote:
> >
> > I have committed the first draft of the PG 18 release notes.
> >
> 
> I think it is worth mentioning about commit
> 7c99dc587a010a0c40d72a0e435111ca7a371c02 as that changes the behavior
> of how the system behaves for missing publications. Previously, we
> used to stop replication with ERROR if the required publication is
> missing, now we skip the missing publication and let replication
> continue. Though it may sound the new behavior is intuitive but still
> there could be some users relying on old behavior, so it is better to
> list this item explicitly.

Huh, looking at the commit message, I can see why I didn't add it:

*  no user reports, only buildfarm
*  used to throw an unexpected error, now works
*  an uncommon failure

We usually don't document those in the release notes.  Can someone else
give an opinion here?

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

  Do not let urgent matters crowd out time for investment in the future.