| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Chris Travers <chris(at)travelamericas(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: How to write jobs in postgresql |
| Date: | 2005-09-09 22:45:54 |
| Message-ID: | 20050909224554.GM7630@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Sep 08, 2005 at 10:27:59AM -0700, Chris Travers wrote:
> Karsten Hilbert wrote:
>
> >>3. An integrated way of logging what ran when (rather than either
> >> stuffing logging code into each cron job or rummaging thru
> >> cron logs)
> >>
> >>
> >Cron can log to syslog.
> >
> >Karsten
> >
> >
> And your cron scripts could log to your database log tables if that is
> what you were getting at.......
True and true, but both of those require more work to setup. I'm not
even sure if you can log only specific cronjobs to syslog.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2005-09-09 23:16:52 | Re: RAID0 and pg_xlog |
| Previous Message | Bricklen Anderson | 2005-09-09 22:17:56 | Re: ERROR: bogus varno |