| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Subject: | Re: Improve heavyweight locks instead of building new lock managers? |
| Date: | 2020-04-10 13:01:47 |
| Message-ID: | CA+TgmobFKOU44zAAjqpa1BSQ7kmdaGzDj4_kPEq_7ZbZ0fbeww@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 19, 2020 at 11:14 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> Here's a *draft* patch series for removing all use of SHM_QUEUE, and
> subsequently removing SHM_QUEUE.
+1 for that idea.
But color me skeptical of what Thomas described as the "incidental
constification".
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James Coleman | 2020-04-10 13:18:38 | Re: Multiple FPI_FOR_HINT for the same block during killing btree index items |
| Previous Message | Robert Haas | 2020-04-10 12:59:53 | Re: Improve heavyweight locks instead of building new lock managers? |