Re: PG optimization question - Mailing list pgsql-performance

From Robert Haas
Subject Re: PG optimization question
Date
Msg-id 603c8f071001101045wb99b337j3e1dabe9ead97421@mail.gmail.com
Whole thread Raw
In response to Re: PG optimization question  (Pierre Frédéric Caillaud<lists@peufeu.com>)
Responses Re: PG optimization question  (Pierre Frédéric Caillaud<lists@peufeu.com>)
List pgsql-performance
2010/1/10 Pierre Frédéric Caillaud <lists@peufeu.com>:
>
>> If you transfer (delete from staging, insert into archive) in one
>> transaction , then it will be always visible in exactly one of them,
>> and exatly once in a view over both staging and archive(s).
>
>        Does the latest version implement this :
>
> INSERT INTO archive (...) DELETE FROM staging WHERE ... RETURNING ...

No.  There are no plans to support that, though there are proposals to support:

WITH x AS (DELETE FROM staging WHERE ... RETURNING ...) INSERT INTO
archive (...) SELECT ... FROM x

I'm not sure how much that will help though since, in the designs so
far discused, the tuples won't be pipelined.

...Robert

pgsql-performance by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Choice of bitmap scan over index scan
Next
From: Robert Haas
Date:
Subject: Re: Choice of bitmap scan over index scan