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

From Andrey Borodin
Subject Re: [HACKERS] pg_background contrib module proposal
Date
Msg-id 20170119174754.9532.57337.pgcf@coridan.postgresql.org
Whole thread Raw
In response to pg_background contrib module proposal  (amul sul <sulamul@gmail.com>)
Responses Re: [HACKERS] pg_background contrib module proposal  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
The following review has been posted through the commitfest application:
make installcheck-world:  tested, passed
Implements feature:       tested, passed
Spec compliant:           tested, passed
Documentation:            tested, failed

I’ll summarize here my thoughts as a reviewer on the current state of the pg_background:
1. Current version of a code [1] is fine, from my point of view. I have no suggestions on improving it. There is no
documentation,but code is commented.
 
2. Patch is dependent on background sessions from the same commitfest.
3. There can exist more features, but for v1 there is surely enough features.
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.
 
Summarizing these points, appropriate statuses of the patch are ‘Ready for committer’ or ‘Rejected’. Between these two
Ichoose ‘Ready for committer’, I think patch is committable (after bg sessions).
 

Best regards, Andrey Borodin.

The new status of this patch is: Ready for Committer

pgsql-hackers by date:

Previous
From: Erik Rijkers
Date:
Subject: Re: [HACKERS] Logical Replication WIP - FailedAssertion, File:"array_typanalyze.c", Line: 340
Next
From: Petr Jelinek
Date:
Subject: Re: [HACKERS] Logical replication existing data copy