Re: pg_dump and --inserts / --column-inserts - Mailing list pgsql-general

From Tom Lane
Subject Re: pg_dump and --inserts / --column-inserts
Date
Msg-id 10812.1279388131@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_dump and --inserts / --column-inserts  (Thomas Kellerer <spam_eater@gmx.net>)
Responses Re: pg_dump and --inserts / --column-inserts  (Thomas Kellerer <spam_eater@gmx.net>)
List pgsql-general
Thomas Kellerer <spam_eater@gmx.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

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Fedora 13 killed dblink this week...
Next
From: Thomas Kellerer
Date:
Subject: Re: pg_dump and --inserts / --column-inserts