Re: pg_upgrade project status
| От | Zdenek Kotala |
|---|---|
| Тема | Re: pg_upgrade project status |
| Дата | |
| Msg-id | 1233180047.1490.15.camel@localhost обсуждение исходный текст |
| Ответ на | Re: pg_upgrade project status (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: pg_upgrade project status
|
| Список | pgsql-hackers |
Tom Lane píše v st 28. 01. 2009 v 14:06 -0500:
> Trying to do catalog upgrade
> in-place is going to be a complete mess. I'd be interested to know,
> for example, how you imagine rearranging the contents of pg_class would
> work. You don't get to modify pg_class if you can't even find it, which
> you can't because you can't read it.
It is relatively easy. There are very high design:
1) upgrade move old catalog table into save location. We can create for
example special tablespace for it
2) bootstrap creates catalog + create records for old catalog structure
3) data will be copied like
INSERT INTO pg_class select from pg_upgrade.pg_class where oid>16...
In reality it will be more complicated command but pure SQL.
Zdenek
В списке pgsql-hackers по дате отправления: