Re: pg_background contrib module proposal

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: amul sul <sulamul(at)gmail(dot)com>, Andrew Borodin <amborodin(at)acm(dot)org>
Cc: Robert Haas <robertmhaas(at)gmail(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: 2016-12-22 21:41:15
Message-ID: 091c037a-3210-2898-5449-e3176885290a@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/22/16 4:20 AM, amul sul wrote:
> • pg_background_detach : This API takes the process id and detach the
> background process. Stored worker's session is not dropped until this
> called.

When I hear "detach" I think that whatever I'm detaching from is going
to stick around, which I don't think is the case here, right? I'd
suggest pg_background_close() instead.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2016-12-22 22:12:18 Re: [BUG?] pg_event_trigger_ddl_commands() error with ALTER TEXT SEARCH CONFIGURATION
Previous Message Jim Nasby 2016-12-22 21:33:52 Re: Potential data loss of 2PC files