| From: | Andreas Seltenreich <seltenreich(at)gmx(dot)de> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | 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>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, 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:04:04 |
| Message-ID: | 87wp4csdaz.fsf@ansel.ydns.eu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards,
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2017-10-03 11:24:16 | Re: [sqlsmith] stuck spinlock in pg_stat_get_wal_receiver after OOM |
| Previous Message | Ildar Musin | 2017-10-03 10:48:43 | Re: Repetitive code in RI triggers |