Re: Use LISTEN/NOTIFY between different databases

Поиск
Список
Период
Сортировка
От Igor
Тема Re: Use LISTEN/NOTIFY between different databases
Дата
Msg-id CALdM5eopyKf-wJLqLuyLwbV6pG2H_YnHFR1a1wRu5Jqr6waZzg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Use LISTEN/NOTIFY between different databases  (John R Pierce <pierce@hogranch.com>)
Ответы Re: Use LISTEN/NOTIFY between different databases  ("Greg Sabino Mullane" <greg@turnstep.com>)
Список 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

В списке pgsql-general по дате отправления:

Предыдущее
От: "Albe Laurenz"
Дата:
Сообщение: Re: Difference between speed of 2 functions: SQL+STABLE and PLPGSQL+EXECUTE
Следующее
От: Clemens Eisserer
Дата:
Сообщение: Re: Is there a tool for checking database integrity