| From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Vitaly Burovoy <vitaly(dot)burovoy(at)gmail(dot)com>, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, Jason Dusek <jason(dot)dusek(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: SERIALIZABLE and INSERTs with multiple VALUES |
| Date: | 2016-10-12 21:11:08 |
| Message-ID: | CACjxUsOKvo1AXUoBArWk0FWq15U-6YuBCEb-Vvz-ze_1xDqCuA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Oct 12, 2016 at 3:55 PM, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> On Wed, Oct 12, 2016 at 1:41 PM, Kevin Grittner <kgrittn(at)gmail(dot)com> wrote:
>> Aren't these two completely separate and independent bugs?
>
> Technically they are, but they are both isolated to the same small
> function. Surely it's better to fix them both at once?
If the code is hopelessly intertwined, maybe. Generally it is
better to fix two independent bugs with two independent patches.
It documents things better and make each fix easier to understand.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2016-10-12 22:21:05 | Re: SERIALIZABLE and INSERTs with multiple VALUES |
| Previous Message | Kevin Grittner | 2016-10-12 21:06:43 | Re: SERIALIZABLE and INSERTs with multiple VALUES |