This is truly interesting from a couple of other perspectives. One of which is that the first "procedural language" for MySQL was supposed to be PHP.
Since Postgresql already has four or five languages in the core (plsql, plpgsql, plperl, plpython, plC), and another 5 or so as add ons (plR, plRuby, plPHP, plJ etc...) this is just one more of them. But Postgresql still beat MySQL to the punch.
The other reason it's so interesting is that there was an article out a while back on why using postgresql with stored procs was bad because you'd wind up programming your database in one language and your application layer in another.
With all the languages supported for stored procs in postgresql now, that's really a non-issue.