Re: Reduce WAL logging of INSERT SELECT

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Reduce WAL logging of INSERT SELECT
Date: 2011-08-04 21:03:23
Message-ID: 4E3B091B.8030109@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 08/04/2011 04:55 PM, Tom Lane wrote:
> Bruce Momjian<bruce(at)momjian(dot)us> writes:
>> One thing we don't optimize is INSERT ... SELECT when the table is
>> created or truncated in the same transaction. Seems we could.
>> We optimize CREATE TABLE AS which is effectively SELECT ... INTO using a
>> different syntax. Is this a TODO?
> Considering that SELECT INTO is deprecated, I don't think we should be
> expending effort to encourage people to use it.
>
>

Right, but the original point about INSERT ... SELECT seems reasonable, no?

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Aidan Van Dyk 2011-08-04 21:09:02 Re: mosbench revisited
Previous Message Tom Lane 2011-08-04 20:55:35 Re: Reduce WAL logging of INSERT SELECT