The point is that Postgres scales a very long way. Once you arrive at OpenAI / ChatGPT scale there's no shame in reaching for a dedicated queuing system.

▲

tomnipotent 37 minutes ago | parent [-]

> scales a very long way

This ignores the fine print. It scales a very long way under specific circumstances with specific workloads. The more write-heavy your workload the less eloquently Postgres scales.

For OpenAI's use case you could swap Postgres with MySQL and it would scale just as well.

▲

ballon_monkey 32 minutes ago | parent [-]

If your DB is write heavy, tune it for writes...

	▲	tomnipotent 29 minutes ago \| parent [-]
		You can't tune your way out of this constraint. The heap table and MVCC implementation put a hard ceiling on what can be accomplished without reaching for another tool.