| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Sim Zacks <sim(at)compulab(dot)co(dot)il> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Proposal - asynchronous functions |
| Date: | 2011-04-26 12:25:59 |
| Message-ID: | BANLkTi=kxmhkOcbB3RTxkYuaGgSUmviQHQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 26, 2011 at 3:28 AM, Sim Zacks <sim(at)compulab(dot)co(dot)il> wrote:
> Add an Async command for functions ( ASYNC my_func(var1,var2) ) and add an
> async optional keyword in trigger statements ( CREATE TRIGGER ... EXECUTE
> ASYNC trig_func() ). This should cause an internal session to be started
> that the function or trigger function will run in, disconnected from the
> session it started in.
We've talked about a number of features that could benefit from some
kind of "worker process" facility (e.g. logical replication, parallel
query). So far no one has stepped forward to build such a facility,
and I think without that this can't even get off the ground.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-04-26 12:28:23 | Re: operator classes for index? |
| Previous Message | Andres Freund | 2011-04-26 12:25:10 | Re: Improving the memory allocator |