Hello,
I haven't added that part of code, nor using postgres to be able to
comment on specific points, but my blind guess is that there are many
queries done in between the table locks, like a check if a record exist,
followed by insert/update/delete/..., so just locking on a row might not
prevent
Hey everyone!
We noticed that under high load of registrations and using the pua module we
can reach a state where the PUA table bloats our Postgres to several GB.
However, a SELECT on pua only shows a few hundred entries. The other half
million or so entries are obsoleted but not cleaned up.
T
