Postgres Pro
Downloads
Home   >   mailing lists

Re[2]: Async_Notify - Mailing list pgsql-hackers

From Арсен Арутюнян
Subject Re[2]: Async_Notify
Date
Msg-id 1576236621.238859707@f116.i.mail.ru
Whole thread Raw
In response to Re: Async_Notify  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
Tree view
I'm trying to send a notification from the PG extension directly.
It turns out the mechanism that is used in the async file. (Async_Notify) does not suit me since the function uses oldcontext = MemoryContextSwitchTo (CurTransactionContext); and MemoryContextSwitchTo (oldcontext);
And I did not find the ability to add notification except the Async_Notify function.
 
Now only SPI_execute works ("NOTIFY chanel,’message’", false, 0);
 
P.S. In my extension, there is already a higher function started with oldcontext = MemoryContextSwitchTo (CurTransactionContext); and MemoryContextSwitchTo (oldcontext);
 
 
 
Пятница, 13 декабря 2019, 12:19 +03:00 от Pavel Stehule <pavel.stehule@gmail.com>:
 
Hi
 
pá 13. 12. 2019 v 10:00 odesílatel Арсен Арутюнян <arutar@bk.ru> napsal:
Hello! I wrote my extension for PG and am trying to run Async_Notify from it. But messages come very late! Sometimes only after I execute the notify command from the shell. What am I doing wrong? How to use Async_Notify correctly.
 
 
I am not sure what mechanism do you use.
 
Notify messages are send after successful  end of transaction.
 
Regards
 
Pavel
 
--
Арсен Арутюнян
 
 
--
Арсен Арутюнян
 

pgsql-hackers by date:

Previous
From: "k.jamison@fujitsu.com"
Date:
Subject: RE: [Patch] Optimize dropping of relation buffers using dlist
Next
From: Pavel Stehule
Date:
Subject: Re: Re[2]: Async_Notify