From: Tom Lane <tgl@sss.pgh.pa.us>
To: exclusion@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17395: Assert failed on merge join when foreign range
 partition contains out-of-range value
In-reply-to: <17395-8c326292078d1a57@postgresql.org>
References: <17395-8c326292078d1a57@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Sat, 05 Feb 2022 06:00:01 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <531523.1644076257.1@sss.pgh.pa.us>
Date: Sat, 05 Feb 2022 10:50:57 -0500
Message-ID: <531524.1644076257@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/531524.1644076257%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> The following query:
> [ foreign partition that doesn't contain the expected data ]
> causes an assertion failure with the following stack:

Hm.  I suppose we have to reduce that assert to an actual runtime
test.  More generally, though, it seems like the documentation is
not nearly clear enough that it's on the user's head to make sure
that a foreign partition's contents meet the partition constraint.
Sec. 5.11.2 punts the matter to the CREATE FOREIGN TABLE man page,
which is okay, but CREATE FOREIGN TABLE doesn't lay it out with
any degree of clarity either.

			regards, tom lane