| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | 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 |
| Date: | 2018-10-19 02:52:51 |
| Message-ID: | 8213.1539917571@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> writes:
> On 2018/10/18 20:57, PG Bug reporting form wrote:
>> I tried to use declarative partitioning and, to avoid creating partitions by
>> hand, to make them in ON BEFORE STATEMENT trigger. Trigger executes
>> successfully (proved that with RAISE NOTICE), but server crashes.
> The problem here is with the server allowing to create a partition of the
> table being inserted into, inside the table's BEFORE INSERT trigger.
> Generally speaking, the command that's run inside the trigger shouldn't
> have been allowed to proceed if it might change the table's properties
> that the execution of the ongoing command is depending upon.
Check.
> I propose the attached to fix that.
Hmm ... I wonder if we shouldn't do CheckTableNotInUse for *both* cases,
is_partition or no?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2018-10-19 03:16:52 | BUG #15440: pg_dump does not preserve quoted identifiers for statement-level trigger transition table names |
| Previous Message | Amit Langote | 2018-10-19 02:40:34 | Re: BUG #15437: Segfault during insert into declarative partitioned table with a trigger creating partition |