possible problems with large objects (connection busy )

[volkmarbuehringer]

Hi,

I am using pgx 4.6 and go 1.14
I use pgxpool for the db-connections.

I use largeObjects for streaming documents out of postgres into a POST request.
If the Post request aborts I have sometimes problems with busy conn on this transaction.

The closing of the large object and rollback of the transaction doesn't work because of this error.
I tried to discard the remaining data of the large object but this doesn't work either.

The only thing I could do is to isolate the large object access into an extra transaction, so the rest of the program can still work. So I have only errors from largeobject.Close and tx.Rollback.

Is there another way to clean the unfinished reader from the post-Request ?

Thanks.

[jackc]

Do you have a way of reproducing this? It's hard to determine whether the issue is pgx or how the application is using it from just the description.

[bfontaine]

Closing this since it’s not reproducible and the issue is two-years old.