From: | Igor <igorya(dot)inscriptio(at)gmail(dot)com> |
---|---|
To: | John R Pierce <pierce(at)hogranch(dot)com> |
Cc: | PostgreSQL <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Use LISTEN/NOTIFY between different databases |
Date: | 2012-05-08 06:53:17 |
Message-ID: | CALdM5eopyKf-wJLqLuyLwbV6pG2H_YnHFR1a1wRu5Jqr6waZzg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> Its real situation. We use sharded cluster based on plproxy. The calling
>> function for DB queries is equal in all databases (see plproxy
>> documentation). Now we need to release some internal logic between clients
>> based on certain events which occurred in this functions. The LISTEN/NOTIFY
>> mechanism is very good feature, but event occur NOT in connected DB - i.e.
>> in destination DB via plproxy wrapper. I.e. wee need subject.
>>
>
> then maybe you could have a process to do this work which connects to all
> the databases and issues the LISTENs and initiates whatever actions you
> need in the other database(s) ?
>
>
>
Yes, but it is workaround. The native way - is the "communication" on
DB-backend level.
It would be very good feature - possibility to set a destination DB in
NOTIFY command as optional argument.
Is the developers read this list ? :)
> --
> john r pierce N 37, W 122
> santa cruz ca mid-left coast
>
>
--
Regards
From | Date | Subject | |
---|---|---|---|
Next Message | Alban Hertroys | 2012-05-08 07:09:35 | Re: FATAL: lock file "postmaster.pid" already exists |
Previous Message | Clemens Eisserer | 2012-05-08 06:52:37 | Re: Is there a tool for checking database integrity |