| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Initial release notes created for 9.6 |
| Date: | 2016-05-05 20:29:47 |
| Message-ID: | 20160505202947.7kqjan7at4q3jrlj@alap3.anarazel.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2016-05-05 16:25:38 -0400, Robert Haas wrote:
> On Thu, May 5, 2016 at 1:32 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > Please review and comment before Monday, if you can.
>
> Overall, I think this looks pretty great. Thanks for pulling it
> together so quickly.
+1
> +<!--
> +2016-04-10 [008608b9d] Avoid the use of a separate spinlock to protect a LWLock
> +-->
> + <para>
> + Use atomic operations, rather than a spinlock, to protect an LWLock's
> + wait queue (Andres Freund)
> + </para>
> + </listitem>
> +
> + <listitem>
>
> This was basically an attempt to cure a defect in 48354581a and could
> perhaps be lumped under that item.
It's also an independent performance improvement (sadly), and has the
potential for issues; so there's *some* benefits on keeping this as its
own entry.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-05-05 20:32:38 | Re: quickdie doing memory allocations (was atomic pin/unpin causing errors) |
| Previous Message | Robert Haas | 2016-05-05 20:29:26 | Re: [sqlsmith] Failed assertion in BecomeLockGroupLeader |