Re: preventing deadlocks - Mailing list pgsql-admin

From Tsirkin Evgeny
Subject Re: preventing deadlocks
Date
Msg-id 43C0D3F1.1090306@mail.jct.ac.il
Whole thread Raw
In response to Re: preventing deadlocks  ("Jim C. Nasby" <jnasby@pervasive.com>)
Responses Re: preventing deadlocks  ("Jim C. Nasby" <jnasby@pervasive.com>)
List 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?

pgsql-admin by date:

Previous
From: Robert Treat
Date:
Subject: Re: [DOCS] technical papers
Next
From: "Sistemas C.M.P."
Date:
Subject: postgresql.conf