| From: | "Marko Kreen" <markokr(at)gmail(dot)com> |
|---|---|
| To: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com> |
| Cc: | "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: Lazy xid assignment V3 |
| Date: | 2007-09-03 12:53:44 |
| Message-ID: | e51f66da0709030553k4dd476b0xe68714a7195352e4@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
On 9/3/07, Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> Florian G. Pflug wrote:
> > Since we didn't really reach an agreement on how xid_age should behave,
> > I've reverted it back to the original version. So with this patch,
> > xid_age will just force assignment of a xid.
>
> Is this really a good idea? I'm repeating myself, but a query like
>
> select age(xmin) from bigtable
>
> could accelerate Xid wraparound. If the server is running close to the
> limit it could cause a shutdown to prevent the actual wraparound.
Such query would take only one xid, which should not be a problem?
--
marko
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2007-09-03 13:01:33 | Re: Lazy xid assignment V3 |
| Previous Message | Alvaro Herrera | 2007-09-03 12:37:24 | Re: Lazy xid assignment V3 |