From: | Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com> |
---|---|
To: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
Cc: | joshua(dot)yanovski(at)gmail(dot)com, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql(at)j-davis(dot)com, joe(dot)conway(at)crunchydata(dot)com |
Subject: | Re: In-place updates and serializable transactions |
Date: | 2018-11-19 06:15:23 |
Message-ID: | CAGz5QCKKEFudD--qiOg1=4KSGNixE3X2bHbN=N6RRzvkckgKtw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Nov 16, 2018 at 4:07 AM Kevin Grittner <kgrittn(at)gmail(dot)com> wrote:
>
> I would say this should be considered a resounding success. We should
> probably add an alternative result file to cover this case, but
> otherwise I don't see anything which requires action.
>
As of now, we've added an extra expected file for the same.
> Congratulations on making this work so well!
>
Thanks for developing the serializable module in a nice decoupled architecture.
--
Thanks & Regards,
Kuntal Ghosh
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Demoor | 2018-11-19 07:30:00 | Re: NOTIFY and pg_notify performance when deduplicating notifications |
Previous Message | Amit Kapila | 2018-11-19 06:01:06 | Re: In-place updates and serializable transactions |