On 2015-11-03 09:52:26 +0100, Pavel Stehule wrote: > 2015-11-03 9:35 GMT+01:00 Andres Freund <andres@anarazel.de>: > > > On 2015-11-03 17:19:43 +1100, Haribabu Kommi wrote: > > > With this commit - bde39eed0cafb82bc94c40e95d96b5cf47b6f719, it is not > > possible > > > to execute Notify commands inside a parallel worker. Can't we change > > > it as disable both listen and notify commands inside a background worker? > > > > Well, parallel workers are something different from general background > > workers. I don't see why it'd make sense to allow listen/notify there, > > given the rest of the restrictions? > > > > I though about this possibility and I am thinking, so NOTIFY can be pretty > useful there. > > The background workers can be used for running AT TIME tasks - run import > every 10 minutes. The notification can be useful for starting AFTER tasks > where the required previous steps should be committed. > > If we use workers more for execution custom code (PLpgSQL, PLPython, ...) > then notification mechanism can be interesting (both directions).
Did you actually read what I wrote above? paralell workers != general background workers.
I miss it, I am sorry. My notice is related to background workers
