Re: PG optimization question
От | Pierre Frédéric Caillaud |
---|---|
Тема | Re: PG optimization question |
Дата | |
Msg-id | op.u6c8ooojcke6l8@soyouz обсуждение исходный текст |
Ответ на | Re: PG optimization question (Robert Haas <robertmhaas@gmail.com>) |
Список | pgsql-performance |
On Sun, 10 Jan 2010 19:45:32 +0100, Robert Haas <robertmhaas@gmail.com> wrote: > 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 > Yeah, but it's a lot more user-friendly than SELECT FOR UPDATE, INSERT SELECT, DELETE...
В списке pgsql-performance по дате отправления: