On 9/12/07, Pavan Deolasee <[EMAIL PROTECTED]> wrote:
>
>
> One change that is worh mentioning
> and discussing is that we don't follow HOT chains while fetching tuples
> during
> autoanalyze and autoanalyze would consider all such tuples as DEAD.
> In the worst case when all the tuples in the tabl
On 9/12/07, Tom Lane <[EMAIL PROTECTED]> wrote:
>
>
>
> This seems all wrong to me. We'd only be considering freezing a tuple
> whose xmin precedes the global xmin. If it has a predecessor, that
> predecessor has xmax equal to this one's xmin, therefore also preceding
> global xmin, therefore it
"Pavan Deolasee" <[EMAIL PROTECTED]> writes:
> On 9/12/07, Tom Lane <[EMAIL PROTECTED]> wrote:
>> XXX doesn't the above completely break the anti-wraparound guarantees?
>> And why couldn't we avoid the problem by pruning the previous tuple,
>> which is surely dead?
> We preserve anti-wraparound gu
"Pavan Deolasee" <[EMAIL PROTECTED]> writes:
> On 9/12/07, Tom Lane <[EMAIL PROTECTED]> wrote:
>> XXX the above being the case, why should we bother with all this extra
>> mechanism? Seems we could dispense with "not ready for inserts".
> Without this additional step, while we are building the in
On 9/12/07, Tom Lane <[EMAIL PROTECTED]> wrote:
>
>
> VACUUM FULL
> ---
>
> To make vacuum full work, any DEAD tuples in the middle of an update
> chain need to be removed (see comments at the top of
> heap_prune_hotchain_hard() for details). Vacuum full performs a more
> aggressive pruning
On 9/12/07, Tom Lane <[EMAIL PROTECTED]> wrote:
>
>
>
> VACUUM
> --
>
> There is little change to regular vacuum. It removes dead HOT tuples,
> like pruning does, and cleans up any redirected dead line pointers.
>
> In lazy vacuum, we must not freeze a tuple that is in the middle of an
> update
On 9/12/07, Tom Lane <[EMAIL PROTECTED]> wrote:
>
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Current README.HOT version:
> > ftp://momjian.us/pub/postgresql/mypatches/README.HOT
>
> I've done some further editorializing and wordsmithing on this,
> and marked with XXX some areas that seem
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Current README.HOT version:
> ftp://momjian.us/pub/postgresql/mypatches/README.HOT
I've done some further editorializing and wordsmithing on this,
and marked with XXX some areas that seem like they're still red flags
(or at least inadequately descr
"Pavan Deolasee" <[EMAIL PROTECTED]> writes:
> It would be worth mentioning that columns appearing in predicates
> of partial indexes and expressions of expression indexes are also
> checked. If any of these columns are changed, HOT update is not done.
In discussion a question arose. I don't thi
Pavan Deolasee wrote:
> It would be worth mentioning that columns appearing in predicates
> of partial indexes and expressions of expression indexes are also
> checked. If any of these columns are changed, HOT update is not done.
Added now:
Tuples are checked against expression and
Gregory Stark wrote:
>
> "Bruce Momjian" <[EMAIL PROTECTED]> writes:
>
> > I have taken this, and Pavan's documentation about CREATE INDEX, and
> > worked up an updated README. Comments? Corrections?
>
> Oh, you I think the CREATE INDEX documentation you refer to was actually the
> one I sugge
On 9/4/07, Bruce Momjian <[EMAIL PROTECTED]> wrote:
>
>
> I have taken this, and Pavan's documentation about CREATE INDEX, and
> worked up an updated README. Comments? Corrections?
Thanks Bruce, Heikki, Greg for helping me with the documentation.
> The requirements for doing a HOT update is
On 9/4/07, Gregory Stark <[EMAIL PROTECTED]> wrote:
>
>
> NOTE: This is something likely to change. Current discussions are leading
> towards handling DELETE_IN_PROGRESS and INSERT_IN_PROGRESS from other
> transactions. We would do this by waiting until the transactions owning
> those
> tuples exi
"Bruce Momjian" <[EMAIL PROTECTED]> writes:
> I have taken this, and Pavan's documentation about CREATE INDEX, and
> worked up an updated README. Comments? Corrections?
Oh, you I think the CREATE INDEX documentation you refer to was actually the
one I suggested.
A few tweaks:
> (If we find a
Bruce Momjian wrote:
> Heikki Linnakangas wrote:
>> Tom Lane wrote:
>>> "Pavan Deolasee" <[EMAIL PROTECTED]> writes:
Please see the version 14 of HOT patch attached.
>>> I expected to find either a large new README, or some pretty substantial
>>> additions to existing README files, to document
"Bruce Momjian" <[EMAIL PROTECTED]> writes:
> Heikki Linnakangas wrote:
>
>> Here's an updated version of the README I posted earlier. It now
>> reflects the changes to how pruning works.
>
> I have taken this, and Pavan's documentation about CREATE INDEX, and
> worked up an updated README. Comme
Heikki Linnakangas wrote:
> Tom Lane wrote:
> > "Pavan Deolasee" <[EMAIL PROTECTED]> writes:
> >> Please see the version 14 of HOT patch attached.
> >
> > I expected to find either a large new README, or some pretty substantial
> > additions to existing README files, to document how this all works
17 matches
Mail list logo
