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

From Thomas Kellerer
Subject Re: pg_dump and --inserts / --column-inserts
Date
Msg-id i1rnkv$p16$1@dough.gmane.org
Whole thread Raw
In response to Re: pg_dump and --inserts / --column-inserts  (Craig Ringer <craig@postnewspapers.com.au>)
Responses Re: pg_dump and --inserts / --column-inserts  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Craig Ringer wrote on 17.07.2010 03:13:
> On 17/07/10 04:26, Thomas Kellerer wrote:
>
>> Hmm.
>> For years I have been advocating to always use fully qualified column
>> lists in INSERTs (for clarity and stability)
>> And now I learn it's slower when I do so :(
>
> If you're not doing hundreds of thousands of identical ones at a time,
> it's still very much a good idea. The costs of parsing and transmission
> are usually pretty insignificant, and the readability/maintenance
> benefits are huge.
>
> It's only when dealing with bulk loading that this sort of thing starts
> to be worth thinking about.
>
Thanks for the clarification.

I'm till a bit surprised that parsing the statement _with_ a column list is mesurably slower than withou a column list.

Regards
Thomas

pgsql-general by date:

Previous
From: "Daniel Verite"
Date:
Subject: Re: Efficient Way to Merge Two Large Tables
Next
From: Oleg Bartunov
Date:
Subject: Re: Incorrect FTS result with GIN index