On Mon, May 7, 2012 at 11:52 PM, John R Pierce wrote:
>> 2012/5/7 John R Pierce mailto:pie...@hogranch.com>>
>> On 05/07/12 1:13 PM, Igor wrote:
>> I understand this. But I need "link" between two clients, connected to
>> different databases.
>>
>> Its real situation. We use sharded cluster bas
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> 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 ? :)
> 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
>
On 05/07/12 1:40 PM, Igor wrote:
2012/5/7 John R Pierce mailto:pie...@hogranch.com>>
On 05/07/12 1:13 PM, Igor wrote:
1.Is this possible in future releases ?
2. How I can organize interconnectbetween two clients
connected to different DB? I need call NOTIFY from p
On 05/07/12 1:13 PM, Igor wrote:
1.Is this possible in future releases ?
2. How I can organize interconnectbetween two clients connected to
different DB? I need call NOTIFY from pgsql function in one database
to another LISTEN client in another database.
a listener isn't 'in a database', it
1. Is this possible in future releases ?
2. How I can organize interconnect between two clients connected to
different DB ? I need call NOTIFY from pgsql function in one database to
another LISTEN client in another database.
--
Regards
