| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: POC: Sharing record typmods between backends |
| Date: | 2017-08-13 02:52:57 |
| Message-ID: | CA+Tgmob2uHcZZiBocOzjbZGdgwmL4KOvzaBvt6w0zga-JXZbEg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Aug 11, 2017 at 9:55 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> Well, most of the potential usecases for dsmhash I've heard about so
> far, don't actually benefit much from incremental growth. In nearly all
> the implementations I've seen incremental move ends up requiring more
> total cycles than doing it at once, and for parallelism type usecases
> the stall isn't really an issue. So yes, I think this is something
> worth considering. If we were to actually use DHT for shared caches or
> such, this'd be different, but that seems darned far off.
I think it'd be pretty interesting to look at replacing parts of the
stats collector machinery with something DHT-based.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2017-08-13 03:28:41 | Re: Comment in snapbuild.c file |
| Previous Message | Michael Paquier | 2017-08-13 01:47:38 | Re: Timing-sensitive case in src/test/recovery TAP tests |