Porting dtrace would be useless, Linux has pretty much catched up in that front - the only piece missing is the merge of utrace in the main kernel. In distros like Fedora, which include utrace, you already can use systemtap to probe both the kernel and userspace without problems (sure, it lacks the "final polish" of dtrace, but all the hard has been done)
Postgres is already maintained by third party companies and such... if it was to be bought, a -few- forks would probably still live on. Though, MySQL's copyright was assigned to a single company of its own...is Postgres the same? I'd guess it would be different.
PostgreSQL is a community project, and a group of companies provide support and related services. There's no one to buy, so no single company can have absolute control.
I assume he means something like "if the field is varchar(50) and you dump a 58-character string into it, it should fail rather than truncate." In which case I'm sure you can get that behavior by turning the database on to strict mode.
Which can be changed at runtime by the client. Not good...
Slashdot Mirror
Porting dtrace would be useless, Linux has pretty much catched up in that front - the only piece missing is the merge of utrace in the main kernel. In distros like Fedora, which include utrace, you already can use systemtap to probe both the kernel and userspace without problems (sure, it lacks the "final polish" of dtrace, but all the hard has been done)
Please... an attempt to copy dtrace, and not a very good one at that.
Thank goodness PostgreSQL is both.
8.3 is just around the corner, so if anyone has still not checked it, please, do yourself a favor and read up on what's new, you'll be pleased.
Which can be changed at runtime by the client. Not good...