| From: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade project status |
| Date: | 2009-01-28 22:00:47 |
| Message-ID: | 1233180047.1490.15.camel@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-01-28 22:04:01 | Re: 8.4 release planning |
| Previous Message | Stephen Frost | 2009-01-28 21:28:31 | Re: Column privileges for system catalogs |