| From: | Rory Campbell-Lange <rory(at)campbell-lange(dot)net> |
|---|---|
| To: | Harald Fuchs <hf517(at)protecting(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: [OT] Dilemma about OS <-> Postgres interaction |
| Date: | 2004-06-18 19:48:14 |
| Message-ID: | 20040618194814.GB21345@campbell-lange.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 18/06/04, Harald Fuchs (hf517(at)protecting(dot)net) wrote:
> In article <20040617232536(dot)GB17879(at)campbell-lange(dot)net>,
> Rory Campbell-Lange <rory(at)campbell-lange(dot)net> writes:
>
> > I should have mentioned that we need the messages sent very soon after
> > they have landed in the 'inbox'; otherwise cron would definitely be the
> > way to go -- including an @reboot line.
>
> This rules out a cronjob. How about writing a pl/perlu function which
> sends the mail and calling that function by an AFTER INSERT trigger?
I was trying to avoid having an untrusted language in the database.
After all, this may be the way to do, and I don't need to worry about
daemons or anything like that.
Even further off-topic:
How does a pl/perl function access perl modules? Is there a sensible way
of testing them?
Thanks
Rory
--
Rory Campbell-Lange
<rory(at)campbell-lange(dot)net>
<www.campbell-lange.net>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2004-06-18 19:52:32 | Re: can't win |
| Previous Message | Dann Corbit | 2004-06-18 19:48:02 | Re: can't win |