Re: pg_dump and --inserts / --column-inserts

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Kellerer <spam_eater(at)gmx(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: pg_dump and --inserts / --column-inserts
Date: 2010-07-17 17:35:31
Message-ID: 10812.1279388131@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thomas Kellerer <spam_eater(at)gmx(dot)net> writes:
> Tom Lane wrote on 17.07.2010 16:36:
>> Well, nobody's offered any actual *numbers* here.

> I measured the runtime as seen from the JDBC client and as reported by explain analyze (the last line reading "Total runtime:")

The "runtime" from explain analyze really should not be measurably
different, since it doesn't include parse time or data transmission
time, and you ought to get the same execution plan with or without the
column names. I'd dismiss those numbers as being within experimental
error, except it seems odd that they all differ in the same direction.
The overall times seen from the client seem plausible though;
particularly since we can see an increase in the percentage overhead
as the number of columns increases, which is what you'd expect if
you were accurately measuring a column-name-lookup overhead.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Thomas Kellerer 2010-07-17 17:46:23 Re: pg_dump and --inserts / --column-inserts
Previous Message Tom Lane 2010-07-17 17:21:51 Re: Fedora 13 killed dblink this week...