Re: Use LISTEN/NOTIFY between different databases - Mailing list pgsql-general

From Greg Sabino Mullane
Subject Re: Use LISTEN/NOTIFY between different databases
Date
Msg-id 9e7e314c08e3d291afc895026dc5d49f@biglumber.com
Whole thread Raw
In response to Re: Use LISTEN/NOTIFY between different databases  (Igor <igorya.inscriptio@gmail.com>)
List pgsql-general
-----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 ? :)

Yes, but I find this a very unlikely feature, for a few reasons. First,
there is a completely acceptable "workaround", as you call it. Second, you
are the first person in my recollection to ask for this, so there is
obviously not a high demand. Third, anything that goes cross-database
is subject to lots of very careful care and handling, and I doubt adding
that complexity is worth the small benefit gained.

- --
Greg Sabino Mullane greg@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201205081059
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAk+pNOwACgkQvJuQZxSWSsjtdACggxjMfNxJxdfiY2ElxrWyx4E7
E/sAoLnDvepVy6QqhVicLf67kmSB6IqV
=oy5d
-----END PGP SIGNATURE-----



pgsql-general by date:

Previous
From: Antonio Goméz Soto
Date:
Subject: 2 machines, same database, same query, 10 times slower?
Next
From: "Tomas Vondra"
Date:
Subject: Re: 2 machines, same database, same query, 10 times slower?