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

From: Thomas Kellerer <spam_eater(at)gmx(dot)net>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: pg_dump and --inserts / --column-inserts
Date: 2010-07-17 07:55:12
Message-ID: i1rnkv$p16$1@dough.gmane.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Oleg Bartunov 2010-07-17 10:53:09 Re: Incorrect FTS result with GIN index
Previous Message Daniel Verite 2010-07-17 07:18:28 Re: Efficient Way to Merge Two Large Tables