Citing CockroachDB as an example of scaling Postgres made me spit out coffee. Was this LLM-written?

sorentwo 3 hours ago | parent | next [-]

The efforts we've undergone to make Oban (and Pro) work with CRDB have been ridiculous. Feature detection all over because of a lack of common operators and functions that can't be used in indexes. The worst is the rampant "serialization_failure" errors that force continual transaction retries. Not how I'd suggest scaling Postgres.

That said, as a predecessor to dbos in building durable workflows just using Postgres, I concur with the overall sentiment.

▲

bcooke 2 hours ago | parent [-]

Can you expand on why you chose to use CRDB with Oban? I have no opinion here, I’m genuinely curious as someone using Oban myself (with Postgres). I haven’t hit the point of really needing to scale it out yet and I’d rather avoid the traps others have figured out.

	▲	TkTech 2 hours ago \| parent [-]
		sorentwo is the author of Oban. He's not using CockroachDB, he's supporting it as a valid Oban target.

▲

Reubend 2 hours ago | parent | prev [-]

Yeah that seems off to me too. But I guess they meant that since CockroachDB is compatible with Pg, it would also serve the same prupose?