Re: Upgrade from PG12 to PG - Mailing list pgsql-admin

From Jef Mortelle
Subject Re: Upgrade from PG12 to PG
Date
Msg-id b5fa55f1-7f6b-5e10-a3d5-52436ee47738@gmail.com
Whole thread Raw
In response to Re: Upgrade from PG12 to PG  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: Upgrade from PG12 to PG
List pgsql-admin

Yes,
But create text allows you to store more data,


8.3. Character Types

Table 8.4. Character Types

NameDescription
character varying(n), varchar(n)variable-length with limit
character(n), char(n)fixed-length, blank padded
textvariable 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

pgsql-admin by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Upgrade from PG12 to PG
Next
From: Scott Ribe
Date:
Subject: Re: Upgrade from PG12 to PG