On Wed, Nov 17, 2021 at 09:54:14PM +0000, Robert Creager wrote: > We are able to move up to Postgres 13.5, in our ports tree, if that would help. We used pg_upgrade to get from 9.6 to 13.3, so that should work fine going instead to 13.5. We’re almost branching/releasing our code, so it’s not a good time, but if it may help with this problem, we’ll deal with it. To be clear, I have no specfic reason to believe it would help. But it would be silly to chase down a problem that someone already fixed 10 months ago (the source of this problem, or something else that comes up). In fact I suspect it won't help, and there's an issue with your schema, or autovacuum, or postgres. Note that since v10, the version scheme uses only two components, and 13.3 to 13.5 is a minor release, similar to 9.6.3 to 9.6.5. So you don't need to use pg_upgrade - just update the binaries. https://www.postgresql.org/docs/13/release-13-5.html -- Justin
