Re: Feedback on getting rid of VACUUM FULL - Mailing list pgsql-hackers

From Albe Laurenz
Subject Re: Feedback on getting rid of VACUUM FULL
Date
Msg-id D960CB61B694CF459DCFB4B0128514C203937F1F@exadv11.host.magwien.gv.at
Whole thread Raw
In response to Re: Feedback on getting rid of VACUUM FULL  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Feedback on getting rid of VACUUM FULL
List pgsql-hackers
Tom Lane wrote:
> > I don't see any reason why not breaking the user visible behavior of
> > tuples CTID between any two major releases,
>
> > Am I completely wet here?
>
> Completely.  This is a user-visible behavior that we have encouraged
> people to rely on, and for which there is no easy substitute.

I second that: it would hurt to lose this generic technique for
optimistic locking.

Yours,
Laurenz Albe


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Hot Standby 0.2.1
Next
From: Simon Riggs
Date:
Subject: Re: Feedback on getting rid of VACUUM FULL