shivasaxena

[dead]

> But that was done by regulation, wasn't it? Would have been nicer to see that come as a result of competition.

Bill Gurly has been crying for years now about how US banks have been bocking/not-participating in equivalent services in US(Fed Now) and for good business reasons for them.

A well functioning market does need regulations. Not everything can be magically fixed by "competition"

https://www.linkedin.com/posts/kivatinos_bill-gurley-on-paym...

shivasaxena

10 mesi fadiscuss

[dead]

shivasaxena

10 mesi fadiscuss

[dead]

shivasaxena

10 mesi fadiscuss

[dead]

shivasaxena

anno scorsodiscuss

Yes, we already have all of our business logic in postgres functions(create_order, create_partial_payment etc).

Doing the extra work in stored procedures is noticeably faster than relying on triggers.

shivasaxena

anno scorsodiscuss

Out of curiosity: Would appreciate if others can share what other things like AccessExclusiveLock should postgres users beware of?

What I already know

- Unique indexes slow inserts since db has to acquire a full table lock

- Case statements in Where break query planner/optimizer and require full table scans

- Read only postgres functions should be marked as `STABLE PARALLEL SAFE`

shivasaxena

anno scorsodiscuss

Yeah, I'm going to remove triggers in next deploy of a POS system since they are adding 10-50ms to each insert.

Becomes a problem if you are inserting 40 items to order_items table.

comments