Re: BUG #17877: Referencing a system column in a foreign key leads to incorrect memory access

From: Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>
To: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Subject: Re: BUG #17877: Referencing a system column in a foreign key leads to incorrect memory access
Date: 2023-03-31 16:45:19
Message-ID: CAEudQAr_71CR6w1aHNHk4T=FDvwu9YVSBubtEP3B=sik8XesKw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

I think that commit f0d65c0
<https://github.com/postgres/postgres/commit/f0d65c0eaf05d6acd3ae05cde4a31465eb3992b2>
has an oversight.

Attnum == 0, is system column too, right?

All other places at tablecmds.c, has this test:

if (attnum <= 0)
ereport(ERROR,

regards,
Ranier Vilela

Attachment Content-Type Size
reject_system_column_equal_zero.patch application/octet-stream 615 bytes

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2023-03-31 16:49:40 Re: SQL/JSON revisited
Previous Message Andres Freund 2023-03-31 16:15:33 Re: regression coverage gaps for gist and hash indexes