You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this something that is even needed? We could open a transaction at the DB layer and then execute multiple write_message functions, however, is that something that is desired? Or should we allow the runtime to deal with that?
There are some pros and cons to each approach. If the runtime must manage the writes, then it is possible that you will have a partial success, which will require logic to recover from. However, this will potentially allow for more throughput at the DB layer because postgres transactions lock, which means if I'm writing a large batch of message in a transaction it will lock others from writing.
Maybe both modes could exist together?
The text was updated successfully, but these errors were encountered:
Is this something that is even needed? We could open a transaction at the DB layer and then execute multiple
write_message
functions, however, is that something that is desired? Or should we allow the runtime to deal with that?There are some pros and cons to each approach. If the runtime must manage the writes, then it is possible that you will have a partial success, which will require logic to recover from. However, this will potentially allow for more throughput at the DB layer because postgres transactions lock, which means if I'm writing a large batch of message in a transaction it will lock others from writing.
Maybe both modes could exist together?
The text was updated successfully, but these errors were encountered: