Re: synchronized snapshots

Поиск
Список
Период
Сортировка
От Joachim Wieland
Тема Re: synchronized snapshots
Дата
Msg-id CACw0+13N-XuT-zi7WkRTK1LKZjsNt_sowMu+iXdwP9K+96=HVw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: synchronized snapshots  (Jim Nasby <jim@nasby.net>)
Ответы Re: synchronized snapshots  (Robert Haas <robertmhaas@gmail.com>)
Re: synchronized snapshots  (Jim Nasby <jim@nasby.net>)
Список pgsql-hackers
On Mon, Aug 15, 2011 at 6:09 PM, Jim Nasby <jim@nasby.net> wrote:
> I suspect that all the other cases of BEGIN failing would be syntax errors, so
> you would immediately know in testing that something was wrong. A missing file
> is definitely not a syntax error, so we can't really depend on user testing to ensure
> this is handled correctly. IMO, that makes it critical that that error puts us in an
> aborted transaction.

Why can we not just require the user to verify if his BEGIN query
failed or succeeded?
Is that really too much to ask for?

Also see what Robert wrote about proxies in between that keep track of
the transaction
state. Consider they see a BEGIN query that fails. How would they know
if the session
is now in an aborted transaction or not in a transaction at all?


Joachim


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: Should we have an optional limit on the recursion depth of recursive CTEs?
Следующее
От: Jim Nasby
Дата:
Сообщение: Re: our buffer replacement strategy is kind of lame