Ah yes. This goes into the "Philip Wishful Thinking" category. There are a few problems with that. First, the Postgres team didn't accept Philip's offer, as they had better things to do than write a new parser. Second, the Oracle syntax is not necessarily the best syntax to copy from a technical standpoint.
The Postgres team is implementing outer joins with an Oracle compatibility mode, so that's good. There are bogus things in Oracle, though, like the varchar(4000) limit which forces CLOB usage. Postgres's lztext extension will give us 32K varchar storage, which is exactly the size of a textarea. Now *that* is web-savvy. In the end, it's very conceivable that Postgres will be a more web-savvy database than Oracle.
