Re: Errors creating partitioned tables from existing using (LIKE <table>) after renaming table constraints

From: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Stuart <sfbarbee(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Errors creating partitioned tables from existing using (LIKE <table>) after renaming table constraints
Date: 2018-12-17 03:55:56
Message-ID: f051179f-15c0-c436-dd01-abc99b7bc5ce@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2018/12/17 12:52, Michael Paquier wrote:
> On Mon, Dec 17, 2018 at 11:20:14AM +0900, Amit Langote wrote:
>> On 2018/12/17 11:06, Michael Paquier wrote:
>>> It seems that the call to relation_close should happen after
>>> CacheInvalidateRelcache. Damn..
>
> That was the issue and this is actually exactly like what has been fixed
> in 8082bea2.
>
>> What a blunder! Sorry. :(
>
> No problem. I have committed a fix after reproducing the failure
> manually and checking the fix. This should cool down prion now.

Thank you!

Regards,
Amit

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2018-12-17 05:14:39 Re: ALTER INDEX ... ALTER COLUMN not present in dump
Previous Message Michael Paquier 2018-12-17 03:52:17 Re: Errors creating partitioned tables from existing using (LIKE <table>) after renaming table constraints