pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chapman Flack <jcflack@acm.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: tighten generic_option_name, or store more carefully in catalog?
Date: Mon, 2 Jun 2025 14:43:49 -0400
Message-ID: <683DF0E5.1040905@acm.org> (raw)
In-Reply-To: <557970.1748888023@sss.pgh.pa.us>
References: <6830EB30.8090904@acm.org>
	<3020890.1748735715@sss.pgh.pa.us>
	<683BA390.7000903@acm.org>
	<3029560.1748740373@sss.pgh.pa.us>
	<683BBE52.8050900@acm.org>
	<557970.1748888023@sss.pgh.pa.us>

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






view thread (8+ messages)  latest in thread

Message-ID: <683DF0E5.1040905@acm.org>
Permalink:  ../683DF0E5.1040905@acm.org/
Also on:    postgresql.org/message-id/683DF0E5.1040905@acm.org

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: jcflack@acm.org, tgl@sss.pgh.pa.us
  Subject: Re: tighten generic_option_name, or store more carefully in catalog?
  In-Reply-To: <683DF0E5.1040905@acm.org>

* 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