pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Steven Flatt <steven.flatt@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Very long SQL strings
Date: Thu, 21 Jun 2007 14:33:01 -0400
Message-ID: <357fa7590706211133u2ae43d09id1653ca63d7a7838@mail.gmail.com> (raw)

I can't seem to find a definitive answer to this.

It looks like Postgres does not enforce a limit on the length of an SQL
string.  Great.  However is there some point at which a query string becomes
ridiculously too long and affects performance?  Here's my particular case:
consider an INSERT statement where you're using the new multi-row VALUES
clause or SELECT ... UNION ALL to group together tuples.  Is it always
better to group as many together as possible?

For example, on a toy table with two columns, I noticed about a 20% increase
when bulking together 1000 tuples in one INSERT statement as opposed to
doing 1000 individual INSERTS.  Would this be the same for 10000? 100000?
Does it depend on the width of the tuples or the data types?

Are there any values A and B such that grouping together A tuples and B
tuples separately and running two statements, will be faster than grouping
A+B tuples in one statement?

Steve

view thread (7+ messages)  latest in thread

Message-ID: <357fa7590706211133u2ae43d09id1653ca63d7a7838@mail.gmail.com>
Permalink:  ../357fa7590706211133u2ae43d09id1653ca63d7a7838@mail.gmail.com/
Also on:    postgresql.org/message-id/357fa7590706211133u2ae43d09id1653ca63d7a7838@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: steven.flatt@gmail.com
  Subject: Re: Very long SQL strings
  In-Reply-To: <357fa7590706211133u2ae43d09id1653ca63d7a7838@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox