| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
| Cc: | Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal: Multiversion page api (inplace upgrade) |
| Date: | 2008-06-13 16:18:37 |
| Message-ID: | 12071.1213373917@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> writes:
> It does not solve problems for example with TOAST tables. If chunks does not fit
> on a new page layout one of the chunk tuple have to be moved to free page. It
> means you get a lot of pages with ~2kB of free unused space. And if max chunk
> size is different between version you got another problem as well.
> There is also idea to change compression algorithm for 8.4 (or offer more
> varinats). It also mean that you need to understand old algorithm in a new
> version or you need to repack everything on old version.
I don't have any problem at all with the idea that in-place update isn't
going to support arbitrary changes of parameters, such as modifying the
toast chunk size. In particular anything that is locked down by
pg_control isn't a problem.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2008-06-13 16:24:48 | Re: Overhauling GUCS |
| Previous Message | Tom Lane | 2008-06-13 16:15:24 | Re: default client encoding in postgresql.conf |