Re: Refactoring speculative insertion with unique indexes a little

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)heroku(dot)com>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Subject: Re: Refactoring speculative insertion with unique indexes a little
Date: 2016-03-15 00:04:39
Message-ID: CA+TgmoaYyVBrQr_n=x4zWkYre9bZvfu7qR4K4BUOxOn50CcfvQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Mar 12, 2016 at 5:53 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> On Sat, Mar 12, 2016 at 2:43 PM, Michael Paquier
> <michael(dot)paquier(at)gmail(dot)com> wrote:
>> Only one version of this patch has been sent at the beginning of this
>> thread, and Heikki has clearly expressed his disagreement about at
>> least a portion of it at the beginning of this thread, so I find it
>> hard to define it as an "uncontroversial" thing and something that is
>> clear to have as things stand. Seeing a new version soon would be a
>> good next step I guess.
>
> What is the point in saying this, Michael? What purpose does it serve?

Gee, I think Michael is right on target. What purpose does writing
him an email that sounds annoyed serve?

There hasn't been a new version of this patch in 9 months, you're
clearly not in a hurry to produce one, and nobody else seems to feel
strongly that this is something that needs to be done at all. I think
we could just let this go and be just fine, but instead of doing that
and moving onto patches that people do feel strongly about, we're
arguing about this. Bummer.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Vitaly Burovoy 2016-03-15 00:12:37 Re: [PATCH] Integer overflow in timestamp[tz]_part() and date/time boundaries check
Previous Message Kouhei Kaigai 2016-03-15 00:03:40 Re: Reworks of CustomScan serialization/deserialization