Tony Caduto schrieb:
> Tino Wildenhain wrote:
>
>> How do you stop your server sending mail in case a transaction goes
>> wild and is sending mails for every updated row in a some megs table?
>>
>
> It would not be smart to send a email via a trigger that updates or
> inserts 1000s of rows would it? All the times I have used PL Perl to
> send a email that has NEVER been the case.
>
> I agree that for a super busy server that is running a website or
> something I probably would not do it that way(most would send the email
> via PHP or whatever). BUT for a GUI client server application(not web
> based) it's more than acceptable especially when the emails are being
> sent internally to a internal mail server where the connection/send time
> is low. It also does not have to be called from a trigger you could
> just call it from another function.
>
> It's not that difficult to catch and handle exceptions in a 8.1 or 8.0
We do not talk about exceptions here. I'm talking about transactions.
And you never know who will be aborting a transaction after your
call to the function. No need for referral to the fine manuals :-)
++Tino
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
