From: | David Gagnon <dgagnon(at)siunik(dot)com> |
---|---|
To: | Marek Lewczuk <newsy(at)lewczuk(dot)com> |
Cc: | Lista dyskusyjna pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: the best way to catch table modification |
Date: | 2005-10-25 17:40:43 |
Message-ID: | 435E6E1B.2010406@siunik.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
I posted on the same subject a month ago . .you can search for the
current title in the JDBC mailing list
[JDBC] implementing asynchronous notifications PLEASE CONFIRM MY
I ended using statement-level trigger. I haven't found another way to
do it .
Regards
/David
Marek Lewczuk wrote:
> Hello,
> I'm implementing db-queries caching system - for this I need to know
> each table's modification time (or at least modification counter). I
> know that I can make a statement-level trigger, which will update a
> table with tables modification times - however this is inefficient if
> many inserts or updates are made on single table (in single
> transaction). The best would be some kind of transaction-level
> trigger, but this is not available. Are there any other, better options ?
>
> Thanks in advance.
> ML
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andrus | 2005-10-25 18:01:57 | Re: Select all invalid e-mail addresses |
Previous Message | Tom Lane | 2005-10-25 17:37:39 | Re: STL problem in stored procedures |