pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: exclusion@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17877: Referencing a system column in a foreign key leads to incorrect memory access
Date: Thu, 30 Mar 2023 11:57:40 +0200
Message-ID: <20230330095740.irhck6e5zbt3jqer@alvherre.pgsql> (raw)
In-Reply-To: <3994000.1680106346@sss.pgh.pa.us>

On 2023-Mar-29, Tom Lane wrote:

> PG Bug reporting form <noreply@postgresql.org> writes:
> > The following query:
> > CREATE TABLE pt(tid oid, id int, PRIMARY KEY(tid, id));
> > CREATE TABLE ft(id int, FOREIGN KEY (tableoid, id) REFERENCES pt);
> > produces a valgrind-detected error:
> 
> We should probably just disallow system columns as foreign keys.
> There was a legitimate use-case for that with OID columns, but
> no more.

+1

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/





view thread (4+ messages)  latest in thread

Message-ID: <20230330095740.irhck6e5zbt3jqer@alvherre.pgsql>
Permalink:  ../20230330095740.irhck6e5zbt3jqer@alvherre.pgsql/
Also on:    postgresql.org/message-id/20230330095740.irhck6e5zbt3jqer@alvherre.pgsql

 · 

reply

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: alvherre@alvh.no-ip.org, tgl@sss.pgh.pa.us, exclusion@gmail.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #17877: Referencing a system column in a foreign key leads to incorrect memory access
  In-Reply-To: <20230330095740.irhck6e5zbt3jqer@alvherre.pgsql>

* 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