From: Glen Parker <glenebob@nwlink.com>
To: pgsql-general@postgresql.org
Subject: Re: Is there anyway to...
Date: Thu, 02 Nov 2006 11:02:59 -0800
Message-ID: <454A40E3.40007@nwlink.com> (raw)
In-Reply-To: <454A3EB6.8080806@linuxlouis.net>
References: <20061102171624.GE21312@localhost>
<454A357E.6010409@linuxlouis.net>
<454A394C.7020102@zijn-digital.com>
<454A3EB6.8080806@linuxlouis.net>
louis gonzales wrote:
> Hey Brian,
> Yeah I had considered this, using cron, I just feel like that is too dirty.
>
> Actually I didn't see Andreas' post, can someone forward that?
>
> I'm running this application on Solaris 9. Ultimately what I want to
> know is, is there something that is internal to postgresql that can be
> used that doesn't need external action, to make it do some task?
>
> Some built in function that can be set to do some simple task on a daily
> - or other time - interval, where all of the defined users may not have
> any activity with the database for day's or week's at a time, but this
> builtin function still operates?
>
> Am I making any sense with how I'm asking this? I could of course have
> cron do a scheduled task of checking/incrementing/decrementing and
> define triggers to occur when one of the cron delivered actions sets the
> appropriate trigger off, but are there other methods that are standard
> in the industry or are we stuck with this type of external influence?
Just some commentary... This is exactly the sort of thing cron is for.
Duplicating that functionality in the RDBMS would be silly IMO. I
don't see why you could consider cron to be "dirty" for this application...
-Glen
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: glenebob@nwlink.com, pgsql-general@postgresql.org
Subject: Re: Is there anyway to...
In-Reply-To: <454A40E3.40007@nwlink.com>
* 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