pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tsirkin Evgeny <tsurkin@mail.jct.ac.il>
To: Jim C. Nasby <jnasby@pervasive.com>
Cc: Tsirkin Evgeny <tsurkin@jct.ac.il>
Cc: pgsql-admin@postgresql.org
Subject: Re: preventing deadlocks
Date: Sun, 08 Jan 2006 10:57:21 +0200
Message-ID: <43C0D3F1.1090306@mail.jct.ac.il> (raw)
In-Reply-To: <20060105210210.GX43311@pervasive.com>
References: <43B10E07.7010503@mail.jct.ac.il>
	<20051228202607.GA5194@wolff.to>
	<Pine.GSO.4.58_heb2.09.0601021131080.10840@ketubot.jct.ac.il>
	<20060104003001.GY82560@pervasive.com>
	<Pine.GSO.4.58_heb2.09.0601041035520.7100@ketubot.jct.ac.il>
	<20060105065747.GA17322@wolff.to>
	<43BCDA17.6070806@mail.jct.ac.il>
	<20060105084030.GA32572@wolff.to>
	<43BCDE94.3030902@mail.jct.ac.il>
	<20060105210210.GX43311@pervasive.com>


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?



view thread (12+ messages)  latest in thread

Message-ID: <43C0D3F1.1090306@mail.jct.ac.il>
Permalink:  ../43C0D3F1.1090306@mail.jct.ac.il/
Also on:    postgresql.org/message-id/43C0D3F1.1090306@mail.jct.ac.il

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tsurkin@mail.jct.ac.il, jnasby@pervasive.com, tsurkin@jct.ac.il
  Subject: Re: preventing deadlocks
  In-Reply-To: <43C0D3F1.1090306@mail.jct.ac.il>
  References: <43B10E07.7010503@mail.jct.ac.il> <20051228202607.GA5194@wolff.to> <Pine.GSO.4.58_heb2.09.0601021131080.10840@ketubot.jct.ac.il> <20060104003001.GY82560@pervasive.com> <Pine.GSO.4.58_heb2.09.0601041035520.7100@ketubot.jct.ac.il> <20060105065747.GA17322@wolff.to> <43BCDA17.6070806@mail.jct.ac.il> <20060105084030.GA32572@wolff.to> <43BCDE94.3030902@mail.jct.ac.il> <20060105210210.GX43311@pervasive.com> <43C0D3F1.1090306@mail.jct.ac.il>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox