From: Tom Lane <tgl@sss.pgh.pa.us>
To: m.michkov@arenadata.io
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18613: Incorrect output for foreign tables with NOT NULL constraints
Date: Thu, 12 Sep 2024 09:54:48 -0400
Message-ID: <4013671.1726149288@sss.pgh.pa.us> (raw)
In-Reply-To: <18613-08a94418126ae1a0@postgresql.org>
References: <18613-08a94418126ae1a0@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> If foreign table data contains nulls while the table definition specifies a
> NOT NULL constraint, some queries return wrong outputs.
How is that not user error?
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, m.michkov@arenadata.io, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18613: Incorrect output for foreign tables with NOT NULL constraints
In-Reply-To: <4013671.1726149288@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