Re: [HACKERS] pg_background contrib module proposal - Mailing list pgsql-hackers

From Andrew Borodin
Subject Re: [HACKERS] pg_background contrib module proposal
Date
Msg-id CAJEAwVGY3zLpYgdYYFN3ZwBJWhp5bNMfoYQJcXAT25F-DsxO-w@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] pg_background contrib module proposal  (amul sul <sulamul@gmail.com>)
Responses Re: [HACKERS] pg_background contrib module proposal  (amul sul <sulamul@gmail.com>)
List pgsql-hackers
Hi!

2017-01-07 11:44 GMT+05:00 amul sul <sulamul@gmail.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.



pgsql-hackers by date:

Previous
From: Andrey Borodin
Date:
Subject: Re: [HACKERS] autonomous transactions
Next
From: Fabien COELHO
Date:
Subject: Re: [HACKERS] pgbench - allow to store select results intovariables