| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Pierre Frédéric Caillaud <lists(at)peufeu(dot)com> |
| Cc: | Hannu Krosing <hannu(at)2ndquadrant(dot)com>, Nickolay <nitro(at)zhukcity(dot)ru>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: PG optimization question |
| Date: | 2010-01-10 18:45:32 |
| Message-ID: | 603c8f071001101045wb99b337j3e1dabe9ead97421@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
2010/1/10 Pierre Frédéric Caillaud <lists(at)peufeu(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-01-11 02:52:25 | Re: Choice of bitmap scan over index scan |
| Previous Message | Kevin Grittner | 2010-01-10 16:01:42 | Re: Choice of bitmap scan over index scan |