Re: Upgrade from PG12 to PG

Поиск
Список
Период
Сортировка
От Jef Mortelle
Тема Re: Upgrade from PG12 to PG
Дата
Msg-id b5fa55f1-7f6b-5e10-a3d5-52436ee47738@gmail.com
обсуждение исходный текст
Ответ на Re: Upgrade from PG12 to PG  (Laurenz Albe <laurenz.albe@cybertec.at>)
Ответы Re: Upgrade from PG12 to PG  (Scott Ribe <scott_ribe@elevated-dev.com>)
Список 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 по дате отправления:

Предыдущее
От: Laurenz Albe
Дата:
Сообщение: Re: Upgrade from PG12 to PG
Следующее
От: Scott Ribe
Дата:
Сообщение: Re: Upgrade from PG12 to PG