News for hackers. Stuff that matters.

A comment on OrioleDB – solving some PostgreSQL wicked problems. Parent comment

Re:OrioleDB – solving some PostgreSQL wicked problems by SigmundA on Friday February 25, 2022 @09:10AM (#30467440)
My only issue is things calling themselves a database when they are either a wrapper layer around an actual DB (most of the new "databases" I see posted) or as in this case a storage engine.

Not trying to take away from the great work done here but the product name and link title would be more clear if it was referred to as a storage engine rather than a DB.

[ Parent | on HN ]
Re:OrioleDB – solving some PostgreSQL wicked problems by thinkx on Monday February 28, 2022 @09:34PM (#30508597)
important distinction - this uses the Postgres Table Access Method to add an additional storage engine to the Postgres platform.. this is NOT a replacement for the current storage engine and can co-exist and be used on a per-table basis
[ Parent | on HN ]
Re:OrioleDB – solving some PostgreSQL wicked problems by marco_craveiro on Saturday February 26, 2022 @01:43PM (#30480416)
Good point. Especially since the final destination is to merge into Postgres mainline in the future, it would make more sense to call this Oriole Storage Engine...
[ Parent | on HN ]