>> No, of course it doesn't. It appears that you didn't look at the repo or
>> read my previous mail before you wrote this.
>
> FFS, I *ran* some of the tests and reported on results. With you in CC.
Just checked back. So you did. I'm sorry, I made the mistake I accused you of.
But... why th
On 2015-07-09 10:30:35 +, Graeme B. Bell wrote:
> > Well, that requires reviewing the source code of the run script and
> > such.
>
> No, of course it doesn't. It appears that you didn't look at the repo or
> read my previous mail before you wrote this.
FFS, I *ran* some of the tests and r
On 08 Jul 2015, at 13:20, Andres Freund wrote:
> On 2015-07-08 11:13:04 +, Graeme B. Bell wrote:
>> I'm guessing you are maybe pressed for time at the moment because I
>> already clearly included this on the last email, as well as the links
>> to the alternative benchmarks with the same prob
On 2015-07-08 11:13:04 +, Graeme B. Bell wrote:
> I'm guessing you are maybe pressed for time at the moment because I
> already clearly included this on the last email, as well as the links
> to the alternative benchmarks with the same problem I referred to on
> both of my last emails which are
On 07 Jul 2015, at 22:52, Merlin Moncure wrote:
> On Tue, Jul 7, 2015 at 3:33 PM, Graeme B. Bell wrote:
>>
>> Hi Merlin,
>>
>> Long story short - thanks for the reply, but you're not measuring anything
>> about the parallelism of code running in a pl/pgsql environment here. You're
>> just me
On Tue, Jul 7, 2015 at 3:33 PM, Graeme B. Bell wrote:
>
> Hi Merlin,
>
> Long story short - thanks for the reply, but you're not measuring anything
> about the parallelism of code running in a pl/pgsql environment here. You're
> just measuring whether postgres can parallelise entering that envir
Hi Merlin,
Long story short - thanks for the reply, but you're not measuring anything
about the parallelism of code running in a pl/pgsql environment here. You're
just measuring whether postgres can parallelise entering that environment and
get back out. Don't get me wrong - it's great that t
On Fri, Jul 3, 2015 at 9:48 AM, Graeme B. Bell wrote:
> Hi everyone,
>
> I've written a new open source tool for easily parallelising SQL scripts in
> postgres. [obligatory plug: https://github.com/gbb/par_psql ]
>
> Using it, I'm seeing a problem that I've also seen in other postgres proje
Hi everyone,
I've written a new open source tool for easily parallelising SQL scripts in
postgres. [obligatory plug: https://github.com/gbb/par_psql ]
Using it, I'm seeing a problem that I've also seen in other postgres projects
involving high degrees of parallelisation in the last 12 mon
