From: Jef Mortelle <jefmortelle@gmail.com>
To: Laurenz Albe <laurenz.albe@cybertec.at>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Upgrade from PG12 to PG
Date: Thu, 20 Jul 2023 16:49:05 +0200
Message-ID: <b5fa55f1-7f6b-5e10-a3d5-52436ee47738@gmail.com> (raw)
In-Reply-To: <a0a7dceb61ab4ae3b2178566684fd3bdf087e698.camel@cybertec.at>
References: <3901e0da-819b-5b6d-bb57-c29f6d384725@gmail.com>
<CAG95seWz3dJxKQPg4_3EAEBCXUuJTDpZBUKAp0+bqP2amQaZ9g@mail.gmail.com>
<dc88d14d-6d0f-2d67-ecfc-c7495bf1c22b@gmail.com>
<a0a7dceb61ab4ae3b2178566684fd3bdf087e698.camel@cybertec.at>
Yes,
But create text allows you to store more data,
8.3. Character Types
*Table 8.4. Character Types*
Name Description
|character varying(/|n|/)|, |varchar(/|n|/)| variable-length with limit
|character(/|n|/)|, |char(/|n|/)| fixed-length, blank padded
|text| variable unlimited length
On 20/07/2023 16:46, Laurenz Albe wrote:
> On Thu, 2023-07-20 at 15:46 +0200, Jef Mortelle wrote:
>> 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.
> To clarify: "text" is no problem at all. Large objects are.
>
> Yours,
> Laurenz Albe
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: jefmortelle@gmail.com, laurenz.albe@cybertec.at, pgsql-admin@lists.postgresql.org
Subject: Re: Upgrade from PG12 to PG
In-Reply-To: <b5fa55f1-7f6b-5e10-a3d5-52436ee47738@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