Whether this is a good idea is another question entirely. Lots of people will tell you it's a horrid idea for PG functions to cause outside-the-database side effects. The reason is that if the transaction that called the function aborts later, there is no way to roll back what was done outside the database, and so the state outside the database will no longer be in sync with the state inside.
By the way - an interesting note. Since MySQL 5.0 has full support for 2PC and XA from now is the first time that MySQL and PostgreSQL can participate in the same transaction :D
Perhaps people might start using the two databases together to harness the power of each? :)
Chris ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
