Re: [sqlsmith] stuck spinlock in pg_stat_get_wal_receiver after OOM

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Andreas Seltenreich <seltenreich(at)gmx(dot)de>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: [sqlsmith] stuck spinlock in pg_stat_get_wal_receiver after OOM
Date: 2017-10-03 11:24:16
Message-ID: 20171003112416.s5bk67p5iatoquhl@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andreas Seltenreich wrote:
> Michael Paquier writes:
>
> > I am attaching a patch that addresses the bugs for the spin lock sections.
> > [2. text/x-diff; walreceiver-spin-calls.patch]
>
> I haven't seen a spinlock PANIC since testing with the patch applied.
> They occured five times with the same amount of testing done earlier.

Thanks for testing. I'm about to push something.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2017-10-03 11:33:57 Re: parallelize queries containing initplans
Previous Message Andreas Seltenreich 2017-10-03 11:04:04 Re: [sqlsmith] stuck spinlock in pg_stat_get_wal_receiver after OOM