Marc,
Since I (and I don't believe anyone else on core) uses Java ...
shouldn't it be up to the developer of the PL/J* modules to do this? We
can't weigh which one is better then the other, as we don't use it ...
Of course the contributors should supply as much of this material as
possible. The point I'm trying to make is that there's often no
incentive to do so, nor a good place to put it.
Also, how does someone support something that they don't use? Again,
that is the developer of PL/J*'s job to do, not ours ...
Again, I'm not trying to offload work from the contributors onto the
members of core. This is about how things are perceived by the
PostgreSQL customers. Of course the contributors must continue to
support their products. If they don't, I'd expect the "supported" status
to be dropped at some point.
At that rate, we'll have to distribute via CD to anyone that wants
PostgreSQL ... cause downloading it via FTP won't be a viable option
anymore :)
In times when people download gigabytes of film and music using
BitTorrent, I think that's the least of our problems. But of course, the
distribution should be kept at a reasonable size. That's why I'd like a
better solution to replace the inferior one and to limit the number of
overlaps.
Regards,
Thomas Hallgren
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
