Re: [**EXTERNAL**] Re: [pgsql-admin] "Soft-hitting" the 1600 columnlimit

Поиск
Список
Период
Сортировка
От Ron
Тема Re: [**EXTERNAL**] Re: [pgsql-admin] "Soft-hitting" the 1600 columnlimit
Дата
Msg-id 44426d65-82a6-3ac5-958e-e7582ecaa7bd@gmail.com
обсуждение исходный текст
Ответ на Re: [**EXTERNAL**] Re: [pgsql-admin] "Soft-hitting" the 1600 columnlimit  ("Moradhassel, Kavian" <kmoradha@ciena.com>)
Ответы Re: [**EXTERNAL**] Re: [pgsql-admin] "Soft-hitting" the 1600 column limit  ("David G. Johnston" <david.g.johnston@gmail.com>)
Список pgsql-admin
Дерево обсуждения
On 06/06/2018 01:54 PM, Moradhassel, Kavian wrote:

To my mind, it makes perfect sense for columns to persist in the table structure when dropped…the only question I have is whether the column would survive a VACUUM FULL?  i.e. if the table is rewritten after the column is dropped, would that change things?

 

Kav Moradhassel | Ciena

kmoradha@ciena.com | 385 Terry Fox Drive | Ottawa, ON, K2K 0L1  Canada


+1

Another solution would be to dump/drop/create/load just that table.

--
Angular momentum makes the world go 'round.

В списке pgsql-admin по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: [pgsql-admin] "Soft-hitting" the 1600 column limit
Следующее
От: "David G. Johnston"
Дата:
Сообщение: Re: [**EXTERNAL**] Re: [pgsql-admin] "Soft-hitting" the 1600 column limit