Re: Errors creating partitioned tables from existing using (LIKE) after renaming table constraints - Mailing list pgsql-bugs
From Michael Paquier
Subject Re: Errors creating partitioned tables from existing using (LIKE) after renaming table constraints
Date
Msg-id 20181217020634.GC31474@paquier.xyz
Whole thread Raw
In response to Re: Errors creating partitioned tables from existing using (LIKE) after renaming table constraints  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Errors creating partitioned tables from existing using (LIKE) after renaming table constraints  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
List pgsql-bugs
On Mon, Dec 17, 2018 at 10:51:10AM +0900, Michael Paquier wrote:
> Done just a few moments ago.  I have also added a test with a primary
> key rename which does not matter as long as LIKE INCLUDE INDEXES is
> involved but that felt safer in the long-run.

Buildfarm member prion is complaining on that:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2018-12-17%2001%3A46%3A36
This uses -DRELCACHE_FORCE_RELEASE -DCATCACHE_FORCE_RELEASE.

It seems that the call to relation_close should happen after
CacheInvalidateRelcache.  Damn..
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Errors creating partitioned tables from existing using (LIKE) after renaming table constraints
Next
From: Amit Langote
Date:
Subject: Re: BUG #15552: Unexpected error in COPY to a foreign table in atransaction