Re: preventing deadlocks

From: Tsirkin Evgeny <tsurkin(at)mail(dot)jct(dot)ac(dot)il>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Cc: Tsirkin Evgeny <tsurkin(at)jct(dot)ac(dot)il>, pgsql-admin(at)postgresql(dot)org
Subject: Re: preventing deadlocks
Date: 2006-01-08 08:57:21
Message-ID: 43C0D3F1.1090306@mail.jct.ac.il
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin


Jim C. Nasby wrote:

>Personally, I'd just put the effort into setting up the insert/delete
>stuff and a means to periodically roll that info up into a summary
>table. I know that this has come up in the past, so you can probably
>find someone else who's already done this and might be able to provide
>you with code. Even if you have to write it from scratch, I doubt it's
>more work than what you've already put into trying to get the other
>scheme to work.
>
Thanks.Do you think that using LISTEN/NOTIFY mechanism for rolling up
the summary table
could be used?

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Sistemas C.M.P. 2006-01-09 17:07:39 postgresql.conf
Previous Message Robert Treat 2006-01-07 18:41:37 Re: [DOCS] technical papers