Re: Reduce WAL logging of INSERT SELECT - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Reduce WAL logging of INSERT SELECT
Date
Msg-id 201108042146.p74LkZX21818@momjian.us
Whole thread Raw
In response to Re: Reduce WAL logging of INSERT SELECT  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Reduce WAL logging of INSERT SELECT
Re: Reduce WAL logging of INSERT SELECT
List pgsql-hackers
Andrew Dunstan wrote:
> 
> 
> On 08/04/2011 04:55 PM, Tom Lane wrote:
> > Bruce Momjian<bruce@momjian.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?

Right.  I brought up SELECT INTO because you could make the argument
that INSERT ... SELECT is not a utility command like the other ones and
therefore can't be done easily, but CREATE TABLE AS is internal SELECT
INTO and implemented in execMain.c, which I think is where INSERT ...
SELECT would also be implemented.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: error: could not find pg_class tuple for index 2662
Next
From: Simon Riggs
Date:
Subject: Re: Reduce WAL logging of INSERT SELECT