Re: Performance features the 4th - Mailing list pgsql-hackers

From Stephen
Subject Re: Performance features the 4th
Date
Msg-id 7vfqb.14072$5C1.10192@nntp-post.primus.ca
Whole thread Raw
In response to Performance features the 4th  (Jan Wieck <JanWieck@Yahoo.com>)
List pgsql-hackers
Yes, I would like to see the vacuum delay patch go into 7.4.1 if possible.
It's really useful. I don't think there is any major risk in adding the
delay patch into a minor revision given the small amount of code change.

Stephen


""Matthew T. O'Connor"" <matthew@zeut.net> wrote in message
news:3FA97470.3020803@zeut.net...
> Tom Lane wrote:
>
> >Jan Wieck <JanWieck@Yahoo.com> writes:
> >
> >
> >>As a matter of fact, people who have performance problems are likely to
> >>be the same who have upgrade problems. And as Gaetano pointed out
> >>correctly, we will see wildforms with one or the other feature applied.
> >>
> >>
> >
> >I'd believe that for patches of the size of my original VACUUM-delay
> >hack (or even a production-grade version of same, which'd probably be
> >10x larger).  The kind of wholesale rewrite you are currently proposing
> >is much too large to consider folding back into 7.4.*, IMHO.
> >
> >
> Do people think that the VACUUM-delay patch by itself, would be usefully
> enough on it's own to consider working it into 7.4.1 or something?  From
> the little feedback I have read on the VACUUM-delay patch used in
> isolation, it certainly does help.  I would love to see it put into 7.4
> somehow.
>
> The far more rigorous changes that Jan is working on, will be welcome
> improvements for 7.5.
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>




pgsql-hackers by date:

Previous
From: elein
Date:
Subject: Re: [pgsql-www] Changes to Contributor List
Next
From: Reinhard Max
Date:
Subject: Re: Erroneous PPC spinlock code