On Mon, Mar 23, 2015 at 10:06 AM, Gavin Flower
<GavinFlower@archidevsys.co.nz> wrote:
> On 23/03/15 13:59, Michael Paquier wrote:
>>
>> On Mon, Mar 23, 2015 at 9:49 AM, Joshua Kramer <joskra42.list@gmail.com>
>> wrote:
>>>
>>> Did anyone catch this comment?
>>>
>>>
>>> http://news.dice.com/2015/03/19/why-i-choose-postgresql-over-mysqlmariadb/#comment-2638712
>>>
>>> Given the stories I've heard about Postgres working well in that type of
>>> application, I'm wondering what out-of-the-ordinary thing that
>>> application
>>> did to cause Postgres to lock up as he said it did.
>>
>> This comment does not mention the version used, but it mentions the
>> JSON features of a "couple of months back", so I would guess that they
>> tried with 9.4.0 and jsonb. Now I recall as well the following bug:
>>
>> http://www.postgresql.org/message-id/20140731233051.GN17765@andrew-ThinkPad-X230
>>
>> And it has been fixed by Alvaro here, included in 9.4.1:
>> commit: 0e3a1f71dfb31527c07a80ccba815b2928d70d8f
>> author: Alvaro Herrera <alvherre@alvh.no-ip.org>
>> date: Fri, 26 Dec 2014 13:52:27 -0300
>> Grab heavyweight tuple lock only before sleeping
>>
>> So perhaps it was the problem they faced?
>> Regards,
>
> I did not see any mention of a bug being raised.
Yep, there were none.
> Perhaps someone could contact the guy directly? He might privately reveal
> the pg version & the companies involved, I wonder what their story is!
>
> I think it would be good if there was a follow on comment from a postgres
> developer...
>
> I assume that it is not simply sophisticated trolling.
I'll just reply there.
--
Michael
