News for hackers. Stuff that matters.

A comment on Oracle customers confirm data stolen in alleged cloud breach is valid. Parent comment

Re:Oracle customers confirm data stolen in alleged cloud bre... by fulafel on Friday March 28, 2025 @12:56AM (#43501677)
PostGIS seems leaps better to me (like the PG DX in other aspects). Eg in Oracle you don't have 2d points. Adding a geo index can fail in the middle and leave the table in a unusable state that requires DBA magic to untangle. Etc.

This is just on top of the general technical inferiority (eg there are no transactional schema changes, so you don't get the safe go/no-go in those when applying those as part of app deploys with a migration tool)

[ Parent | on HN ]
Re:Oracle customers confirm data stolen in alleged cloud bre... by cess11 on Friday March 28, 2025 @03:29AM (#43502529)
SDO_POINT(x, y, 0) or SDO_POINT(x, y, NULL) ought to do what you want. Index corruption can be a nasty problem on Postgres too.

You need to decide if and how to perform a rollback, similar to how you would define a down() procedure in migration files. A schema change might imply changes to data, and in that case you might turn off client writes, copy the table, change it, validate, do rename dance, turn on client writes again. If it doesn't it might be much cheaper to operate on a single copy. How does Postgres decide on such strategies automatically?

[ Parent | on HN ]