Re: Oh, this is embarrassing: init file logic is still broken

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Oh, this is embarrassing: init file logic is still broken
Date: 2015-06-26 22:47:24
Message-ID: 558DD67C.3020502@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 6/25/15 12:51 PM, Josh Berkus wrote:
> On 06/25/2015 10:47 AM, Peter Geoghegan wrote:
>> On Wed, Jun 24, 2015 at 2:52 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>>> OK, this is pretty bad in its real performance effects. On a workload
>>> which is dominated by new connection creation, we've lost about 17%
>>> throughput.
>>
>> Mistakes happen, but this is the kind of regression that automated
>> performance testing could have caught. That's another area of testing
>> that needs considerable improvement IMV.
>
> Well, I have a pgbench test script for it now. If only I had some place
> to check it in ...

Well, there is https://github.com/slux/PostgreSQL-Performance-Farm; but
it hasn't been touched in 5 years. :(
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Data in Trouble? Get it in Treble! http://BlueTreble.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2015-06-26 22:47:48 Re: UPSERT on partition
Previous Message Peter Geoghegan 2015-06-26 22:39:19 Re: 9.5 release notes