From: | David Fetter <david(at)fetter(dot)org> |
---|---|
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 14:02:21 |
Message-ID: | 20110426140221.GA20033@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Apr 26, 2011 at 04:17:48PM +0300, Sim Zacks wrote:
> On 04/26/2011 03:15 PM, Merlin Moncure wrote:
>
> >On Tue, Apr 26, 2011 at 3:28 AM, Sim Zacks<sim(at)compulab(dot)co(dot)il> wrote:
> >>Asynchronous functions
> >>
> >>*Problem*
> >>Postgresql does not have support for asynchronous function calls.
> >Well, there is asynchronous support from the client of course. Thus
> >you can set up a asynchronous call back to the database with dblink.
> >There is some discussion about formalizing this feature -- you might
> >want to read up on autonomous transactions and how they might be used
> >to do what you are proposing.
> >
> >merlin
> I am looking for specifically server support and not client support.
> Part of the proposal is that if the client goes away, it will still
> continue to finish.
This is exactly autonomous transactions. Please read this thread to
see how.
http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2011-04-26 14:17:49 | pg_upgrade fix for connection testing |
Previous Message | Merlin Moncure | 2011-04-26 13:43:30 | Bad COMPACT_ALLOC_CHUNK size in tsearch/spell.c? |