Re: [PATCH] Lazy xid assingment V2

Поиск
Список
Период
Сортировка
Искать
От
Heikki Linnakangas
Тема
Re: [PATCH] Lazy xid assingment V2
Дата
Msg-id
46DBBF0A.1040708@enterprisedb.com
Ответ на
Список
Дерево обсуждения
[PATCH] Lazy xid assingment V2 "Florian G. Pflug" <fgp@phlo.org>
Re: [PATCH] Lazy xid assingment V2 Tom Lane <tgl@sss.pgh.pa.us>
Re: [PATCH] Lazy xid assingment V2 "Florian G. Pflug" <fgp@phlo.org>
Re: [PATCH] Lazy xid assingment V2 Tom Lane <tgl@sss.pgh.pa.us>
Re: [PATCH] Lazy xid assingment V2 "Florian G. Pflug" <fgp@phlo.org>
Re: [PATCH] Lazy xid assingment V2 Tom Lane <tgl@sss.pgh.pa.us>
Re: [PATCH] Lazy xid assingment V2 Alvaro Herrera <alvherre@commandprompt.com>
Re: [PATCH] Lazy xid assingment V2 "Florian G. Pflug" <fgp@phlo.org>
Re: [PATCH] Lazy xid assingment V2 Gregory Stark <stark@enterprisedb.com>
Re: [PATCH] Lazy xid assingment V2 "Florian G. Pflug" <fgp@phlo.org>
Re: [PATCH] Lazy xid assingment V2 Tom Lane <tgl@sss.pgh.pa.us>
August Zajonc wrote:
> The thing is, the leak occurs in situation where a COMMIT hasn't
> returned to the user, so we are trying to guarantee no data-loss even
> when the user doesn't see a successful commit? That's a tall order
> obviously and hopefully people design their apps to attend to
> transaction success / failure.

No, by the time we'd delete/move to trash the files, we know that
they're no longer needed. But because deleting a relation is such a
drastic thing to do, with potential for massive data loss, we're being
extra paranoid. What if there's a bug in PostgreSQL that makes us delete
the wrong file? Or transaction wraparound happens, despite the
protections that we now have in place? Or you have bad RAM in the
server, and a bit flips at an unfortunate place? That's the kind of
situations we're worried about.

--  Heikki Linnakangas EnterpriseDB   http://www.enterprisedb.com

В списке pgsql-hackers по дате отправления
От: Magnus Hagander
Дата:
От: Oleg Bartunov
Дата:
FAQ