Postgres Pro
Downloads
Home   >   mailing lists

Re: Errors creating partitioned tables from existing using (LIKE) after renaming table constraints - Mailing list pgsql-bugs
From Amit Langote
Subject Re: Errors creating partitioned tables from existing using (LIKE) after renaming table constraints
Date
Msg-id b7ffd062-cd82-c72d-6227-527bb9f42431@lab.ntt.co.jp
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
List pgsql-bugs
Tree view 
On 2018/12/17 11:06, Michael Paquier wrote:
> 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..

What a blunder!  Sorry. :(

Thanks,
Amit

pgsql-bugs by date:

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