From: Ireneusz Pluta <ipluta@wp.pl>
To: Jan Lentfer <Jan.Lentfer@web.de>
Cc: pgsql-sql@postgresql.org
Subject: Re: Job control in sql
Date: Tue, 29 May 2012 12:01:47 +0200
Message-ID: <4FC49E8B.6040006@wp.pl> (raw)
In-Reply-To: <879f6ef6940b25a63a82d87dc0c530c3@neslonek.homeunix.org>
References: <4FBF4293.4090902@krap.dk>
<879f6ef6940b25a63a82d87dc0c530c3@neslonek.homeunix.org>
W dniu 2012-05-25 14:52, Jan Lentfer pisze:
> Add a sort of status table where you insert your unique job identifer at the start of the function
> and remove it in the end? As seperate transactions of course.
That might leave status set on forever in a case when a job crashes and does not reach the point
where it removes the identifier.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: ipluta@wp.pl, Jan.Lentfer@web.de
Subject: Re: Job control in sql
In-Reply-To: <4FC49E8B.6040006@wp.pl>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox