Postgres Pro
Downloads
Home   >   mailing lists

Re: getting ERROR "relation 16401 has no triggers" with partitionforeign key alter - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: getting ERROR "relation 16401 has no triggers" with partitionforeign key alter
Date
Msg-id 20190717223037.GA25510@alvherre.pgsql
Whole thread Raw
In response to Re: getting ERROR "relation 16401 has no triggers" with partitionforeign key alter  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: getting ERROR "relation 16401 has no triggers" with partitionforeign key alter
List pgsql-hackers
Tree view 
On 2019-Jul-17, Alvaro Herrera wrote:

> I think we should just run CheckTableNotInUse for each partition in
> ATExecDropConstraint.  Trying that out now.

Actually, that doesn't fix this problem, because the partitioned side is
the *referencing* side, and ATExecDropConstraint is obsessed about the
*referenced* side only and assumes that the calling code has already
dealt with the referencing side checks.  I'm trying a fix for that now.

I wonder if there are other AT subcommands that are similarly broken,
because many of them skip the CheckTableNotInUse for the partitions.

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

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: getting ERROR "relation 16401 has no triggers" with partitionforeign key alter
Next
From: Andres Freund
Date:
Subject: Re: PG 11 JIT deform failure