Re: Upgrade from PG12 to PG

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


Don't use pg_dumpall.  Use this instead:

pg_dump --format=directory --jobs=X --verbose

On 7/20/23 08:46, Jef Mortelle wrote:

Many thanks for your answer.

So: not possible to have very little downtime if you have a database with al lot rows containing text  as datatype, as pg_upgrade needs 12hr for 24 milj rows in pg_largeobject.

Testing now with pg_dumpall en pg_restore ....

I think, postgresql should take this in high priority to  resolve this problem.

I have to make a choice in the near future: Postgres or Oracle, and that database would have a lot of datatype text.
Database would have 1 TB.
It seems me a little bit tricky/dangerous to use Postgres, just for being able to upgrade to a newer version.

Kind regards.

On 20/07/2023 13:43, Ilya Kosmodemiansky wrote:
Hi Jef,

On Thu, Jul 20, 2023 at 1:23 PM Jef Mortelle <jefmortelle@xxxxxxxxx> wrote:
Looking at the dump file: man many lines like SELECT

I have the same issue with /usr/lib/postgresql15/bin/pg_upgrade -v -p
5431 -P 5432 -k

Whats going on ?
pg_upgrade is known to be problematic with large objects.
Please take a look here to start with:

Kind regards

Born in Arizona, moved to Babylonia.

[Index of Archives]     [Postgresql Home]     [Postgresql General]     [Postgresql Performance]     [Postgresql PHP]     [Postgresql Jobs]     [PHP Users]     [PHP Databases]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Databases]     [Yosemite Forum]

  Powered by Linux