Re: preventing deadlocks

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

On Sun, Jan 08, 2006 at 10:57:21AM +0200, Tsirkin Evgeny wrote:
>
> 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?

Sure, although on a busy system it might be better to just poll once a
minute or so. I'm not sure what the overhead for a NOTIFY is, but I
imagine it would start to add up if you were calling several times a
second.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Jim C. Nasby 2006-01-09 20:35:58 Re: Memory Usage Question
Previous Message Jaime Casanova 2006-01-09 20:22:09 Re: What happens to transactions durring a pg_dump?