Fork me on GitHub
#sql
<
2019-10-03
>
jumar11:10:06

@kulminaator that's an interesting point; so we can view blocking IO (on the DB client side) as a sort of backpressure strategy 🙂. Perhaps it's DB implementations themselves that benefit more from non-blocking operations rather than the DB clients...

dharrigan14:10:09

Ah, much rejoicing, PostgreSQL 12 is out! 🙂

parrot 4
gklijs14:10:49

Anything in particular that's changed/improved?

yogidevbear14:10:56

A work colleague pointed this out: >PostgreSQL 12 introduces the ability to rebuild indexes without blocking writes to an index via the REINDEX CONCURRENTLY command, allowing users to avoid downtime scenarios for lengthy index rebuilds.

seancorfield23:10:33

No. The "friendly" functions are intended to be just sugar for very basic operations. Mostly you should use plan, execute-one!, and execute!.

seancorfield23:10:51

HoneySQL is great.