| From: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
|---|---|
| To: | Daniel Wood <hexexpert(at)comcast(dot)net> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: GetSnapshotData round two(for me) |
| Date: | 2018-09-25 05:55:38 |
| Message-ID: | CAFiTN-tpF=KWTBmSUU8gw2WoVA6LYDfYR-NiZ-ZeLfFj9-7Nmg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Sep 25, 2018 at 11:00 AM, Daniel Wood <hexexpert(at)comcast(dot)net> wrote:
> I was about to suggest creating a single shared snapshot instead of having
> multiple backends compute what is essentially the same snapshot. Luckily,
> before posting, I discovered Avoiding repeated snapshot computation from
> Pavan and POC: Cache data in GetSnapshotData() from Andres.
>
I think Mithun has also worked on this[1] and posted some analysis
about which cases he has seen improvement and also the cases where it
did not perform well, you might want to have a look.
--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2018-09-25 06:22:19 | Re: Strange failure in LWLock on skink in REL9_5_STABLE |
| Previous Message | Daniel Wood | 2018-09-25 05:30:40 | GetSnapshotData round two(for me) |