|From:||Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>|
|To:||Michael Paquier <michael(at)paquier(dot)xyz>|
|Cc:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, skaurus(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org|
|Subject:||Re: BUG #15437: Segfault during insert into declarative partitioned table with a trigger creating partition|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On 2018/10/29 15:57, Michael Paquier wrote:
> On Mon, Oct 29, 2018 at 02:28:53PM +0900, Amit Langote wrote:
>> On 2018/10/29 12:31, Michael Paquier wrote:
>>> In the case of a partition, the execution state relies on the data
>>> inserted, so the restriction sounds fine to me. If one tries to attach
>>> a partition after creating a table you actually get an error:
>>> ERROR: 55006: cannot ALTER TABLE "check_not_in_use" because it is being
>>> used by active queries in this session
>>> CONTEXT: SQL statement "alter table check_not_in_use attach partition
>>> check_not_in_use1 for values IN (1);"
>> Yeah, I forgot to include this example in my previous emails.
> We may want to add a new test for this one in the same spirit as what
> has been sent in the previous patch.
>>> Other callers of CheckTableNotInUse() use command tags, which is
>>> inconsistent here, still I cannot think of anything better than
>>> CREATE TABLE "%s" PARTITION OF
>>> CREATE TABLE .. PARTITION OF
>> Maybe the latter is fine, because we want to highlight the parent table's
>> name, not partition's.
> Fine by me.
Done that way. I also switched the check back to just partitioned parent
Thanks for looking at this.
|Next Message||Sandeep Thakkar||2018-10-29 08:22:29||Re: BUG #15453: Installer registers with major version only|
|Previous Message||Kyotaro HORIGUCHI||2018-10-29 06:58:17||Re: BUG #15449: file_fdw using program cause exit code error when using LIMIT|