Re: "Idle in Transaction" revisited.

Поиск
Список
Период
Сортировка
От Markus Schaber
Тема Re: "Idle in Transaction" revisited.
Дата
Msg-id 20040921095922.145bf883@kingfisher.intern.logi-track.com
обсуждение исходный текст
Ответ на Re: "Idle in Transaction" revisited.  ("John R Pierce" <pierce@hogranch.com>)
Список pgsql-jdbc
Hi,

On Mon, 20 Sep 2004 08:52:29 -0700
"John R Pierce" <pierce@hogranch.com> wrote:

> > Regarding cooperative locking and the fact that after a crash the lock
> > stays: I'm not sure how your application is designed, but in ours after
> > a crash we definitely want it to stay there, so we can manually check
> > the consistency of the data before releasing the lock for further
> > processing. I have bad experience with automatic recovery after crashes.
>
> in this particular case, the lock is to simply indicate there is an active
> 'subscriber' to a messaging 'subject', if the app has exited any which ways,
> by definition that 'subscriber' is no longer active, so yes, we want the
> lock to go away.

Have you ever thought at using LISTEN/NOTIFY for this purpose?

Markus

--
markus schaber | dipl. informatiker
logi-track ag | rennweg 14-16 | ch 8001 zürich
phone +41-43-888 62 52 | fax +41-43-888 62 53
mailto:schabios@logi-track.com | www.logi-track.com

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

Предыдущее
От: "John R Pierce"
Дата:
Сообщение: Re: "Idle in Transaction" revisited.
Следующее
От: Markus Schaber
Дата:
Сообщение: Re: raising the default prepareTheshold