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
Date: Sat, 05 Feb 2022 10:50:57 -0500
Message-ID: <531524.1644076257@sss.pgh.pa.us> (raw)
In-Reply-To: <17395-8c326292078d1a57@postgresql.org>
References: <17395-8c326292078d1a57@postgresql.org>
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
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-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, exclusion@gmail.com, 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: <531524.1644076257@sss.pgh.pa.us>
* 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