yeap... but you have to give up many of the reasons for using meteor. (the dynamic refresh, etc.)

The package is really just a simple wrapper around an npm library.

Because meteor is node-based any db that node has libraries for can be "used" .... at the expense of giving up on most meteor features.

IFRC, postres can notify clients of changes, so you should be able to implement the missing features - that is to say the limitations are artificial at this point

"you should be able to implement the missing features" -- me ?? not hardly - I don't work at Meteor.

Take it up with the Meteor.com people.