Re: Suggestions on message transfer among backends - Mailing list pgsql-hackers

From Kyotaro HORIGUCHI
Subject Re: Suggestions on message transfer among backends
Date
Msg-id 20190312.140126.162563492.horiguchi.kyotaro@lab.ntt.co.jp
Whole thread Raw
In response to Re: Suggestions on message transfer among backends  (Andy Fan <zhihui.fan1213@gmail.com>)
List pgsql-hackers
Hello.

At Mon, 11 Mar 2019 21:37:32 +0800, Andy Fan <zhihui.fan1213@gmail.com> wrote in
<CAKU4AWqhZn1v5CR85J74AAVXnTijWTzy6y-3pbYxqmpL5ETEig@mail.gmail.com>
> notes on the shared hash map:   it needs multi writers and multi readers.
> 
> On Mon, Mar 11, 2019 at 9:36 PM Andy Fan <zhihui.fan1213@gmail.com> 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, but postgre doesn't use it.  is there any
> > equivalent in PG?
> >
> > shared hash map:  the number of items can be fixed and the value can be
> > fixed as well.
> >
> > any keywords or explanation will be extremely helpful.

I suppose that you are writing an extension or tweaking the core
code in C source. dshash (dynamic shared hash) would work for you
as shared hash map, and is shm_mq usable as the message queue?

-- 
Kyotaro Horiguchi
NTT Open Source Software Center



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Why don't we have a small reserved OID range for patch revisions?
Next
From: Michael Paquier
Date:
Subject: Re: Adding a TAP test checking data consistency on standby withminRecoveryPoint