Re: pg_upgrade: How to deal with toast
От | Bruce Momjian |
---|---|
Тема | Re: pg_upgrade: How to deal with toast |
Дата | |
Msg-id | 200811201829.mAKITDS27567@momjian.us обсуждение исходный текст |
Ответ на | Re: pg_upgrade: How to deal with toast (Zdenek Kotala <Zdenek.Kotala@Sun.COM>) |
Ответы |
Re: pg_upgrade: How to deal with toast
|
Список | pgsql-hackers |
Zdenek Kotala wrote: > Tom Lane napsal(a): > > Zdenek Kotala <Zdenek.Kotala@Sun.COM> writes: > >> Heikki Linnakangas napsal(a): > >>> Perhaps we should just add the new attid attribute to the toast table, > >>> but mark it as nullable? > > > >> Hmm, It seems to me as a good idea. > > > > No, it's a really horrid idea. Nullable attributes complicate the C > > code, and what in the world are we buying with it anyway? Just decide > > what the field should contain and put it in there. > > The problem what we try to solve is to perform this change during upgrade from > 8.3->8.4. Extra value is a problem because it requires extra space and there is > not free space. It is temporal solution(hack) for 8.3->8.4. Once we have the 'require free space' capability in a major Postgres release, can't we use that to make space for the new TOAST field we will need? -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
В списке pgsql-hackers по дате отправления: