Re: ERROR: there is no unique constraint matching given keys for referenced table "audit_p"

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Miles Elam <miles(dot)elam(at)productops(dot)com>
Cc: Michael Lewis <mlewis(at)entrata(dot)com>, Shatamjeev Dewan <sdewan(at)nbsps(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: ERROR: there is no unique constraint matching given keys for referenced table "audit_p"
Date: 2019-11-18 20:32:31
Message-ID: CAKFQuwbL=Zff3hEnNgBW2aoxzNm9AqBkBoikBeSgbFjSZ=aMRw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Nov 18, 2019 at 1:01 PM Miles Elam <miles(dot)elam(at)productops(dot)com>
wrote:

> I was under the impression that PostgreSQL 12 removed this limitation. Was
> this incorrect?
>
> https://www.2ndquadrant.com/en/blog/postgresql-12-foreign-keys-and-partitioned-tables/
>

Yeah, as the comments in that article make clear, the new feature has some
rough edges (limitations) that you are hitting with your desired model.

David J.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Peter J. Holzer 2019-11-18 22:24:52 Re: REINDEX VERBOSE unknown option
Previous Message Miles Elam 2019-11-18 20:01:33 Re: ERROR: there is no unique constraint matching given keys for referenced table "audit_p"