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

From Peter Eisentraut
Subject Re: [HACKERS] pg_background contrib module proposal
Date
Msg-id 6c74754e-c98c-845c-2535-9b83d7ba0686@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] pg_background contrib module proposal  (Andrey Borodin <amborodin@acm.org>)
Responses Re: [HACKERS] pg_background contrib module proposal  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 1/19/17 12:47 PM, Andrey Borodin wrote:
> 4. There is some controversy on where implemented feature shall be: in separate extension (as in this patch), in
db_link,in some PL API, in FDW or somewhere else. I think that new extension is an appropriate place for the feature.
ButI’m not certain.
 

I suppose we should decide first whether we want pg_background as a
separate extension or rather pursue extending dblink as proposed elsewhere.

I don't know if pg_background allows any use case that dblink can't
handle (yet).

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] pg_ls_dir & friends still have a hard-coded superuser check
Next
From: Brad DeJong
Date:
Subject: Re: [HACKERS] GSoC 2017