Hacker News
new
|
past
|
comments
|
ask
|
show
|
jobs
|
submit
login
bootsmann
5 days ago
|
parent
|
context
|
favorite
| on:
Building durable workflows on Postgres
Advisory locks are preferred for this anyways because holding a lot of SELECT FOR UPDATE doesn’t scale too well.
Edit: Actually I checked this again and apparently the advice has now changed to the inverse.
help
sgt
5 days ago
[–]
I need to do proper benchmarks on SELECT FOR UPDATE..SKIP LOCKED - but I suspect thousands per second. Some claimed higher than 10k/sec, but we'll see
reply
Guidelines
|
FAQ
|
Lists
|
API
|
Security
|
Legal
|
Apply to YC
|
Contact
Search:
Edit: Actually I checked this again and apparently the advice has now changed to the inverse.