Re: pg_upgrade with large pg_largeobject table

Mate Varga writes: >> Using the large-object API for things that tend to not actually be very >> large (which they aren't, if you've got hundreds of millions of 'em) is an >> antipattern, I'm afraid. > I know :( So maybe I need to do some refactoring in the application and > inline the lobs. The

Re: pg_upgrade with large pg_largeobject table

Thanks. > You mean 250M rows in pg_largeobject itself, or 250M large objects (that is, 250M rows in pg_largeobject_metadata)? 250M large objects. > Are you sure you're using a 64-bit build of pg_dump? file /usr/lib/postgresql/10/bin/pg_dump /usr/lib/postgresql/10/bin/pg_dump: ELF 64-bit LSB s

Re: pg_upgrade with large pg_largeobject table

Mate Varga writes: > We have a PSQL 9.5 DB with 16G physical RAM and ~ 1 TB data mostly stored > in the pg_largeobject system table. This table has 250M rows at the moment. You mean 250M rows in pg_largeobject itself, or 250M large objects (that is, 250M rows in pg_largeobject_metadata)? > This

pg_upgrade with large pg_largeobject table

Hi. hanks in advance for any advice. We have a PSQL 9.5 DB with 16G physical RAM and ~ 1 TB data mostly stored in the pg_largeobject system table. This table has 250M rows at the moment. We're trying to upgrade this to 10.x with an in-place upgrade. The command I'm using is:sudo -u postgres /usr/