Gleipnir/nidus-sync
4
0
Fork 0
Code Issues 18 Pull requests Projects Releases Packages Wiki Activity Actions

Fix notification of job happening before transaction is closed

Browse source 
This is kind of a wild one. Turns out that the triggers I was using
actually fire before the transaction is closed and I was primarily
getting lucky that the job was present on the other side of the
connection rather than having things built correctly.

I've fixed this by removing the trigger entirely and instead manually
triggering as part of the transaction. This makes the NOTIFY call happen
as soon as the transaction closes, just at the cost of making my
application be in charge of ensuring the NOTIFY gets called. Seems like
a win.

Part of doing this is porting the existing job creation code over to use
Jet. It's something I want to do anyway, so it's a win all around.
This commit is contained in:
Eli Ribble 2026-05-22 23:19:31 +00:00
parent 7b04822a9b
commit 393836a86a
No known key found for this signature in database
30 changed files with 1126 additions and 72 deletions
Download patch file Download diff file Expand all files Collapse all files

2
platform/email/email.go
View file

@ -114,7 +114,7 @@ func sendEmailBegin(ctx context.Context, source string, destination string, temp
if err != nil {
return fmt.Errorf("Failed to store email log: %w", err)
}
return background.NewEmailSend(ctx, db.PGInstance.BobDB, *e)
return background.NewEmailSend(ctx, db.PGInstance.PGXPool, *e)
}
func sendEmailComplete(ctx context.Context, email_id int32) error {
bxn := db.PGInstance.BobDB