On 4/8/15 4:58 PM, Tim Uckun wrote:
So is there a third and even faster way of doing this?
Please don't top-post.
On Wed, Apr 8, 2015 at 4:08 PM, Adrian Klaver mailto:adrian.kla...@aklaver.com>> wrote:
On 04/07/2015 07:49 PM, Tim Uckun wrote:
I understand that there is overhead
So is there a third and even faster way of doing this?
On Wed, Apr 8, 2015 at 4:08 PM, Adrian Klaver
wrote:
> On 04/07/2015 07:49 PM, Tim Uckun wrote:
>
>> I understand that there is overhead involved in parsing the strings and
>> such. The amount of overhead was surprising to me but that's ano
On 04/07/2015 07:49 PM, Tim Uckun wrote:
I understand that there is overhead involved in parsing the strings and
such. The amount of overhead was surprising to me but that's another
matter. What I am really puzzled about is the difference between the
statements
EXECUTE 'INSERT INTO ' || quot
I understand that there is overhead involved in parsing the strings and
such. The amount of overhead was surprising to me but that's another
matter. What I am really puzzled about is the difference between the
statements
EXECUTE 'INSERT INTO ' || quote_ident(partition_name) || ' SELECT
($1).*
On 3/12/15 8:15 AM, Tomas Vondra wrote:
On 12.3.2015 04:57, Tim Uckun wrote:
I am using postgres 9.4, the default install with "brew install
postgres, no tuning at all. BTW if I use postgres.app application the
benchmarks run twice as slow!
I have no idea what brew or postgres.app is. But I s
On 12.3.2015 04:57, Tim Uckun wrote:
> I am using postgres 9.4, the default install with "brew install
> postgres, no tuning at all. BTW if I use postgres.app application the
> benchmarks run twice as slow!
I have no idea what brew or postgres.app is. But I strongly recommend
you to do some tunin
I am using postgres 9.4, the default install with "brew install postgres,
no tuning at all. BTW if I use postgres.app application the benchmarks run
twice as slow!
Why do you think there is such dramatic difference between
EXECUTE 'INSERT INTO ' || quote_ident(partition_name) || ' SELECT
($1)
On 11.3.2015 21:43, Tim Uckun wrote:
> Hey I hate to bump my post but I would really appreciate some input
> on this benchmark. I am very alarmed that adding a very simple
> partitioning trigger slows the insert speed by an order of magnitude.
> Is there any way to speed this up?
I think to actual
Hey I hate to bump my post but I would really appreciate some input on this
benchmark. I am very alarmed that adding a very simple partitioning trigger
slows the insert speed by an order of magnitude. Is there any way to speed
this up?
On Mon, Mar 9, 2015 at 11:44 AM, Tim Uckun wrote:
> I wrote
I wrote a quick benchmarking script to test various partitioning
strategies. The code is here.
https://gist.github.com/timuckun/954ab6bdce36fa14bc1c
I was astonished at the variability of the timings between the different
variations.
The test data contained 270K records. I did a simple insert i
10 matches
Mail list logo
