Re: pgsql: Do assorted mop-up in the planner.

From: Robins Tharakan <tharakan(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Do assorted mop-up in the planner.
Date: 2023-02-06 03:43:08
Message-ID: CAEP4nAw8_JdhRsD7uxdNsiRf4Spjp4pXxxfgOhkKbMyc8xRC3A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Mon, 6 Feb 2023 at 05:57, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I'd hoped that some of these failures shared a root cause, but nope
> they were really four different bugs :-(. I've now pushed fixes
> for all four, and I hope you'll turn your fuzzer back on. This
> is very valuable testing.

Thanks Tom for fixing these promptly but more importantly for
confirming that this was helpful... allows for similar effort going forward.

-
robins

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2023-02-06 05:42:08 pgsql: Add support for progress reporting to pg_verifybackup
Previous Message Michael Paquier 2023-02-06 02:23:28 pgsql: Properly NULL-terminate GSS receive buffer on error packet recep