On Thu, Nov 6, 2025 at 3:44 AM Masahiko Sawada wrote:
>
> >
> > I suggest that we should prohibit using tableoid in COPY WHERE clauses
> > for the time being. I don't know if there would be a way to make them
> > work correctly at all, but most likely not in a backpatchable way anyway.
> >
> > I
On Wed, Nov 5, 2025 at 3:06 AM Peter Eisentraut wrote:
>
> I think the COPY FROM WHERE clause is handling the tableoid column in a
> way that is inconsistent with its usual definition.
>
> Consider a partitioning hierarchy like
>
> DROP TABLE IF EXISTS xp;
>
> CREATE TABLE xp (a int, b int) PARTIT
On 05.11.25 12:13, Kirill Reshke wrote:
Looks like this issue is currently discussed at [0]. Should we
continue here or there?
[0]https://www.postgresql.org/message-id/
CACJufxHGGc25a2m%2B3Dezfctuykn51n5k3FJK6w3KSqfSFc5gvQ%40mail.gmail.com
I'm aware of that thread. I started this new thread
On Wed, 5 Nov 2025 at 16:06, Peter Eisentraut wrote:
>
> I think the COPY FROM WHERE clause is handling the tableoid column in a
> way that is inconsistent with its usual definition.
>
> Consider a partitioning hierarchy like
>
> DROP TABLE IF EXISTS xp;
>
> CREATE TABLE xp (a int, b int) PARTITIO
I think the COPY FROM WHERE clause is handling the tableoid column in a
way that is inconsistent with its usual definition.
Consider a partitioning hierarchy like
DROP TABLE IF EXISTS xp;
CREATE TABLE xp (a int, b int) PARTITION BY LIST (a);
CREATE TABLE xp1 PARTITION OF xp FOR VALUES IN (1);
