On 2017-09-13 17:53:44 -0400, Tom Lane wrote:
> Andres Freund writes:
> > Indeed that seems plausible. I guess something like the attached should
> > fix the issue?
>
> Ah, I see you came to the same conclusion I did. But see comment
> about adding a comment.
I've pushed something - Not sure if
On 2017-09-13 14:46:08 -0700, Jeff Janes wrote:
> On Wed, Sep 13, 2017 at 2:41 PM, Andres Freund wrote:
> > Indeed that seems plausible. I guess something like the attached should
> > fix the issue?
> >
>
> Yep, that fixes it.
Cool. Pushed. Thanks for the report!
Thanks,
Andres
--
Sent via
Andres Freund writes:
> Indeed that seems plausible. I guess something like the attached should
> fix the issue?
Ah, I see you came to the same conclusion I did. But see comment
about adding a comment.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-ha
Jeff Janes writes:
> In 10beta4 and 11dev, If I run the below it enters an uninterruptible
> state. After the insert starts, I give 15 or seconds or so until the
> memory usage starts to grow due to enqueued triggers checks. Then I can't
> interrupt it with either ctrl-C in psql or kill -15 from
On Wed, Sep 13, 2017 at 2:41 PM, Andres Freund wrote:
> Hi,
>
> On 2017-09-13 14:28:34 -0700, Jeff Janes wrote:
> > In 10beta4 and 11dev, If I run the below it enters an uninterruptible
> > state. After the insert starts, I give 15 or seconds or so until the
> > memory usage starts to grow due t
Hi,
On 2017-09-13 14:28:34 -0700, Jeff Janes wrote:
> In 10beta4 and 11dev, If I run the below it enters an uninterruptible
> state. After the insert starts, I give 15 or seconds or so until the
> memory usage starts to grow due to enqueued triggers checks. Then I can't
> interrupt it with either
In 10beta4 and 11dev, If I run the below it enters an uninterruptible
state. After the insert starts, I give 15 or seconds or so until the
memory usage starts to grow due to enqueued triggers checks. Then I can't
interrupt it with either ctrl-C in psql or kill -15 from another
terminal.
I have t
