Re: BUG #15451: Error adding foriegn key constraint

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: harry(at)harryclarke(dot)me(dot)uk, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15451: Error adding foriegn key constraint
Date: 2018-10-22 19:12:08
Message-ID: 20181022191208.po23ymm4c45qziqk@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2018-Oct-22, PG Bug reporting form wrote:

> ERROR: constraints on permanent tables may reference only permanent tables
>
> ALTER TABLE bnm.table1
> ADD CONSTRAINT id_fk FOREIGN KEY (bnm_id)
> REFERENCES bnm.table2 (id) MATCH SIMPLE
> ON UPDATE NO ACTION
> ON DELETE NO ACTION;

Is table2 an unlogged table perchance?

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2018-10-22 19:41:30 BUG #15452: 10.5 and reproducible "ERROR: could not read block 0 in file..." when creating functional index
Previous Message Andres Freund 2018-10-22 19:12:07 Re: BUG #15451: Error adding foriegn key constraint