Hi,
In one of our project we are supposed to send the notifications
regarding any row modifications in a perticular table to the external
application which will be implementing the listen event for the same.
We are using the postgress version 8.0.3.
we have observed that pgNotify
[EMAIL PROTECTED] wrote:
Hi,
In one of our project we are supposed to send the notifications
regarding any row modifications in a perticular table to the external
application which will be implementing the listen event for the same.
We are using the postgress version 8.0.3.
Ca
Hi Richard Huxton,
Thank you for your kind response.
Is there not any other way other than record the pkey in a
"process_these" table and have the application check there.We want
to minimise the database transactions to improve the DB performance.
Can we send the
[EMAIL PROTECTED] wrote:
Hi Richard Huxton,
Thank you for your kind response.
Is there not any other way other than record the pkey in a
"process_these" table and have the application check there.We want
to minimise the database transactions to improve the DB performance.
Yes, our application is supposed to know *immediately* that a change in
the database has occurred since, based on this modified data it is doing
lot of other operations and also, the db transactions are heavy(expected
to be arround 300 tps(transactions per sec)).
I agree that this can be done usi
[EMAIL PROTECTED] wrote:
Yes, our application is supposed to know *immediately* that a change in
the database has occurred since, based on this modified data it is doing
lot of other operations and also, the db transactions are heavy(expected
to be arround 300 tps(transactions per sec)).
I agree
On Wed, Jan 03, 2007 at 07:47:34PM +0530, [EMAIL PROTECTED] wrote:
>
> Yes, our application is supposed to know *immediately* that a change in
> the database has occurred since,
NOTIFY doesn't get you that anyway. It's _close_ to immediately, but
it's still asynchronous.
A
--
Andrew Sulliv
On Wed, Jan 03, 2007 at 07:47:34PM +0530, [EMAIL PROTECTED] wrote:
Yes, our application is supposed to know *immediately* that a change in
the database has occurred since,
I'd recommend some sort of "whiteboard" layer or messaging fabric as an
option for this sort of thing. This offloads the
