On: New PostgreSQL Interface for Cloud Spanner

[ellisv]

and I'm out

Lack of JSON(B) is a complete no-go for me

[epberry → ellisv]

jsonb has become the crutch on which I build everything. And I'm not going back.

[e1g → epberry]

Same. PG jsonb is so fantastic that it’s closer to exoskeleton than a crutch.

[babelfish → e1g]

What do you use JSONB columns for? The only use case that comes immediately to mind is stuff like settings or config blobs for individual entities

[e1g → babelfish]

I run a multi-tenant SaaS where every tenant can define custom properties on every entity. PG allows us to dump everything into a single jsonb column, and still have superb performance for filtering / analytics / searching etc. The backend codebase remains mostly agnostic to the data shape, and we rarely have to change the database during new releases.

[derefr → babelfish]

Postgres jsonb + redis_fdw = you can JOIN your structured Postgres data against your unstructured app-layer Redis data. Not a good idea to write any code that does this—just move the Redis data into the DB, for crying out loud—but for BI use-cases where you’re writing one-off SQL queries and you need presentation-layer data that lives in Redis, it’s perfect.

[dboreham → epberry]

PostgreSQL json functions allow me to dispense with the ORM. Just send and receive JSON (for regular table field types, note, not jsonb).

[isuckatcoding → ellisv]

You know it’s funny because I’m looking into using the JSON type for spanner. Is that comparable to JSONB