Re: Suggestions on message transfer among backends

2019-03-14 Thread Antonin Houska
Robert Haas wrote: > On Tue, Mar 12, 2019 at 4:34 AM Antonin Houska wrote: > > Andy Fan wrote: > > > I just don't know why shm_mq is designed to single-reader & single-writer. > > > > shm_mq was implemented as a part of infrastructure for parallel query > > processing. The leader backend launch

Re: Suggestions on message transfer among backends

2019-03-12 Thread Robert Haas
On Tue, Mar 12, 2019 at 4:34 AM Antonin Houska wrote: > Andy Fan wrote: > > I just don't know why shm_mq is designed to single-reader & single-writer. > > shm_mq was implemented as a part of infrastructure for parallel query > processing. The leader backend launches multiple parallel workers and

Re: Suggestions on message transfer among backends

2019-03-12 Thread Antonin Houska
Andy Fan wrote: > I just don't know why shm_mq is designed to single-reader & single-writer. shm_mq was implemented as a part of infrastructure for parallel query processing. The leader backend launches multiple parallel workers and sets up a few queues to communicate with each. One queue is us

Re: Suggestions on message transfer among backends

2019-03-12 Thread Andy Fan
On Tue, Mar 12, 2019 at 2:36 PM Andy Fan wrote: > On Tue, Mar 12, 2019 at 1:59 PM Andrey Lepikhov > wrote: > >> On 11/03/2019 18:36, Andy Fan wrote: >> > Hi: >> >I need some function which requires some message exchange among >> > different back-ends (connections). >> > specially I need a sh

Re: Suggestions on message transfer among backends

2019-03-11 Thread Andy Fan
On Tue, Mar 12, 2019 at 1:59 PM Andrey Lepikhov wrote: > On 11/03/2019 18:36, Andy Fan wrote: > > Hi: > >I need some function which requires some message exchange among > > different back-ends (connections). > > specially I need a shared hash map and a message queue. > > > > Message queue: i

Re: Suggestions on message transfer among backends

2019-03-11 Thread Andrey Lepikhov
On 11/03/2019 18:36, Andy Fan wrote: Hi:   I need some function which requires some message exchange among different back-ends (connections). specially I need a shared hash map and a message queue. Message queue:  it should be many writers,  1 reader.   Looks POSIX message queue should be OK

Re: Suggestions on message transfer among backends

2019-03-11 Thread Kyotaro HORIGUCHI
Hello. At Mon, 11 Mar 2019 21:37:32 +0800, Andy Fan wrote in > notes on the shared hash map: it needs multi writers and multi readers. > > On Mon, Mar 11, 2019 at 9:36 PM Andy Fan wrote: > > > Hi: > > I need some function which requires some message exchange among > > different back-ends

Re: Suggestions on message transfer among backends

2019-03-11 Thread Chapman Flack
On 03/11/19 19:53, Euler Taveira wrote: > Em seg, 11 de mar de 2019 às 10:36, Andy Fan > escreveu: >> >> I need some function which requires some message exchange among different >> back-ends (connections). >> specially I need a shared hash map and a message queue. >> > It seems you are looking

Re: Suggestions on message transfer among backends

2019-03-11 Thread Euler Taveira
Em seg, 11 de mar de 2019 às 10:36, Andy Fan escreveu: > > I need some function which requires some message exchange among different > back-ends (connections). > specially I need a shared hash map and a message queue. > It seems you are looking for LISTEN/NOTIFY. However, if it is part of a com

Re: Suggestions on message transfer among backends

2019-03-11 Thread Andy Fan
notes on the shared hash map: it needs multi writers and multi readers. On Mon, Mar 11, 2019 at 9:36 PM Andy Fan wrote: > Hi: > I need some function which requires some message exchange among > different back-ends (connections). > specially I need a shared hash map and a message queue. > > M