Message-ID: <5457DECE.3070302@dunslane.net>
Date: Mon, 03 Nov 2014 15:00:14 -0500
From: Andrew Dunstan <andrew@dunslane.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: pgsql-perform <pgsql-performance@postgresql.org>
Subject: assignment vs SELECT INTO
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org


I found out today that direct assignment to a composite type is (at 
least in my test) about 70% faster than setting it via SELECT INTO. That 
seems like an enormous difference in speed, which I haven't really been 
able to account for.

Test case:

    andrew=# \d abc
           Table "public.abc"
      Column |  Type   | Modifiers
    --------+---------+-----------
      x      | text    |
      y      | text    |
      z      | integer |
    andrew=# do $x$ declare r abc; begin for i in 1 .. 10000000 loop
    select 'a','b',i into r.x,r.y,r.z; end loop; end; $x$;
    DO
    Time: 63731.434 ms
    andrew=# do $x$ declare r abc; begin for i in 1 .. 10000000 loop r
    := ('a','b',i); end loop; end; $x$;
    DO
    Time: 18744.151 ms


Is it simply because the SELECT is in effect three assignments, so it 
takes nearly 3 times as long?

cheers

andrew


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance