Postgres Pro
Downloads
Home   >   mailing lists

Re: tighten generic_option_name, or store more carefully in catalog? - Mailing list pgsql-hackers

From Chapman Flack
Subject Re: tighten generic_option_name, or store more carefully in catalog?
Date
Msg-id 683DF0E5.1040905@acm.org
Whole thread Raw
In response to tighten generic_option_name, or store more carefully in catalog?  (Chapman Flack <jcflack@acm.org>)
Responses Re: tighten generic_option_name, or store more carefully in catalog?
List pgsql-hackers
Tree view 
On 06/02/25 14:13, Tom Lane wrote:
> Here's a proposed patch for the "=" issue.  Whether or not we should
> rethink FDW validation behavior, doing so surely couldn't be
> back-patched.  But I think this much should be.

LGTM
Regards,
-Chap

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Improve hash join's handling of tuples with null join keys
Next
From: Melanie Plageman
Date:
Subject: Re: Correcting freeze conflict horizon calculation