desdenova
DTDrizzle Team
•Created by I am a Dev on 10/3/2023 in #help
Drizzle support SELECT FOR UPDATE of postgres to avoid logical race conditions ?
i think the same bug could potentially occur in the POOL mode as well in case the connection that's already running a transaction gets reused to run another one, but I'm not sure how it works internally
23 replies
DTDrizzle Team
•Created by I am a Dev on 10/3/2023 in #help
Drizzle support SELECT FOR UPDATE of postgres to avoid logical race conditions ?
23 replies
DTDrizzle Team
•Created by I am a Dev on 10/3/2023 in #help
Drizzle support SELECT FOR UPDATE of postgres to avoid logical race conditions ?
@Angelelz This is a bug in Drizzle and the way it uses
node-postgress in Client mode. Since the Client mode is using only 1 connection, you cannot have more than 1 transaction running at the same time so what happens here is that all the db statements get crammed in a single transaction (concurrent transaction BEGIN statements are treated as one because there is only 1 client)23 replies