On 2020-Aug-27, Ashutosh Bapat wrote:
> On Wed, 26 Aug 2020 at 22:47, Alvaro Herrera
> wrote:
> > But I'm not 100% about running the BEFORE triggers. Maybe
> > one way to address this is to check whether the BEFORE triggers in the
> > new target partition are clones; if so then they would hav
On Wed, 26 Aug 2020 at 22:47, Alvaro Herrera
wrote:
>
> What this is saying to me is that we'd need to make sure to run the
> final target partition's AFTER triggers, not the original target
> partition.
Agreed.
> But I'm not 100% about running the BEFORE triggers. Maybe
> one way to addre
On 2020-Aug-21, Ashutosh Bapat wrote:
> On Fri, Aug 21, 2020 at 1:28 PM movead...@highgo.ca
> wrote:
> > In current BEFORE TRIGGER implementation, it reports an error once a
> > trigger result out of current partition, but I think it should check
> > it after finish all triggers call, and you c
On Fri, Aug 21, 2020 at 1:28 PM movead...@highgo.ca wrote:
>
> Hello hackers,
>
> Currently, if BEFORE TRIGGER causes a partition change, it reports an error
> 'moving row
> to another partition during a BEFORE FOR EACH ROW trigger is not supported'
> and fails
> to execute. I want to try to add
Hello hackers,
Currently, if BEFORE TRIGGER causes a partition change, it reports an error
'moving row
to another partition during a BEFORE FOR EACH ROW trigger is not supported' and
fails
to execute. I want to try to address this limitation and have made an initial
patch to get
feedback from
