| From: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
|---|---|
| To: | "Mark Woodward" <pgsql(at)mohawksoft(dot)com> |
| Cc: | "Heikki Linnakangas" <hlinnaka(at)iki(dot)fi>, "Jan Wieck" <janwieck(at)yahoo(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Csaba Nagy" <nagy(at)ecircle-ag(dot)com>, "Hannu Krosing" <hannu(at)skype(dot)net>, "Christopher Browne" <cbbrowne(at)acm(dot)org>, "postgres hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: vacuum, performance, and MVCC |
| Date: | 2006-06-24 15:37:02 |
| Message-ID: | 36e682920606240837g4c508ef3s62dcbadbfff5d5fe@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/24/06, Mark Woodward <pgsql(at)mohawksoft(dot)com> wrote:
> > On 6/24/06, Mark Woodward <pgsql(at)mohawksoft(dot)com> wrote:
> >> In the scenario, as previously outlined:
> >>
> >> ver001->verN->...->ver003->ver2->|
> >> ^-----------------------------/
> >
> > So you want to always keep an old version around?
>
> Prior to vacuum, it will be there anyway, and after vacuum, the new
> version will become ver001.
So you do intend to move verN into ver001's slot? What about the
other conditions you had mentioned where you have to follow
PostgreSQL's current behavior? How are you going to have a pointer
chain in that case?
--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation | fax: 732.331.1301
33 Wood Ave S, 2nd Floor | jharris(at)enterprisedb(dot)com
Iselin, New Jersey 08830 | http://www.enterprisedb.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2006-06-24 15:55:53 | Re: Exporting type OID macros in a cleaner fashion |
| Previous Message | Magnus Hagander | 2006-06-24 14:57:00 | Re: cygwin breakage (was: GPL Source and Copyright Questions) |