pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Upgrade from PG12 to PG
Date: Thu, 20 Jul 2023 11:59:25 -0500
Message-ID: <9502f877-c699-4f28-4bb3-4cd3753c14da@gmail.com> (raw)
In-Reply-To: <dc88d14d-6d0f-2d67-ecfc-c7495bf1c22b@gmail.com>
References: <3901e0da-819b-5b6d-bb57-c29f6d384725@gmail.com>
	<CAG95seWz3dJxKQPg4_3EAEBCXUuJTDpZBUKAp0+bqP2amQaZ9g@mail.gmail.com>
	<dc88d14d-6d0f-2d67-ecfc-c7495bf1c22b@gmail.com>

Don't use pg_dumpall.  Use this instead:

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

On 7/20/23 08:46, Jef Mortelle wrote:
> Hi,
>
> 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@gmail.com> wrote:
>>> Looking at the dump file: man many lines like SELECT
>>> pg_catalog.lo_unlink('100000');
>>>
>>>
>>> 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:
>> https://www.postgresql.org/message-id/20210309200819.GO2021%40telsasoft.com
>>
>>>
>>> Kind regards
>>>
>>>
>>>
>
>

-- 
Born in Arizona, moved to Babylonia.





view thread (18+ messages)  latest in thread

Message-ID: <9502f877-c699-4f28-4bb3-4cd3753c14da@gmail.com>
Permalink:  ../9502f877-c699-4f28-4bb3-4cd3753c14da@gmail.com/
Also on:    postgresql.org/message-id/9502f877-c699-4f28-4bb3-4cd3753c14da@gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
  Subject: Re: Upgrade from PG12 to PG
  In-Reply-To: <9502f877-c699-4f28-4bb3-4cd3753c14da@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox