From: | Andrew Borodin <borodin(at)octonica(dot)com> |
---|---|
To: | amul sul <sulamul(at)gmail(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, David Fetter <david(at)fetter(dot)org>, Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_background contrib module proposal |
Date: | 2017-01-07 08:36:03 |
Message-ID: | CAJEAwVGY3zLpYgdYYFN3ZwBJWhp5bNMfoYQJcXAT25F-DsxO-w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi!
2017-01-07 11:44 GMT+05:00 amul sul <sulamul(at)gmail(dot)com>:
> Changes:
> 1. pg_background_launch renamed to pg_background_start
> 2. pg_background_detach renamed to pg_background_close
> 3. Added new api to display previously launch background worker & its
> result count waiting to be read.
Great work!
> Note that attached patches need to apply to the top of the Peter
> Eisentraut's v2 patch[1].
I've looked a bit into that patch. I thought you would switch
MemoryContext before calling BackgroundSessionStart() from
pg_background? Have I got something wrong?
Best regards, Andrey Borodin.
From | Date | Subject | |
---|---|---|---|
Next Message | Fabien COELHO | 2017-01-07 09:25:06 | Re: pgbench - allow to store select results into variables |
Previous Message | Andrey Borodin | 2017-01-07 08:30:04 | Re: autonomous transactions |