I assume we no longer need this stats patch from May of 2006.
---
Bruce Momjian wrote:
> Tom Lane wrote:
> > Bruce Momjian writes:
> > > Have we seen any such failures since the first day they appeared?
> >
> > agouti blew
Tom Lane wrote:
> Bruce Momjian writes:
> > Have we seen any such failures since the first day they appeared?
>
> agouti blew up about the same time you typed that, so yes it's still
> a problem.
>
> http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=agouti&dt=2006-05-08%2003:15:01
Delay pgstat
Bruce Momjian writes:
> Have we seen any such failures since the first day they appeared?
agouti blew up about the same time you typed that, so yes it's still
a problem.
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=agouti&dt=2006-05-08%2003:15:01
regards, tom lane
Tom Lane wrote:
> Bruce Momjian writes:
> > Was this fixed somehow? I don't see any more buildfarm failures, but I
> > didn't see a fix go in either. It is very possible the pgport fix I did
> > yesterday is related, but I have not applied it yet.
>
> It's an intermittent failure; the fact you
Bruce Momjian writes:
> Was this fixed somehow? I don't see any more buildfarm failures, but I
> didn't see a fix go in either. It is very possible the pgport fix I did
> yesterday is related, but I have not applied it yet.
It's an intermittent failure; the fact you don't see any at this instan
Magnus Hagander wrote:
> > >>> This was not ready to be applied, was it?
> >
> > > I don't recall any specific objections that weren't answered.
> >
> > How about the fact that it's already caused one buildfarm failure?
> >
> > http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=wasp&dt=2006
> -04
> >>> This was not ready to be applied, was it?
>
> > I don't recall any specific objections that weren't answered.
>
> How about the fact that it's already caused one buildfarm failure?
>
> http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=wasp&dt=2006
-04-30%2003:05:01
Well, that objection c
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
>>> This was not ready to be applied, was it?
> I don't recall any specific objections that weren't answered.
How about the fact that it's already caused one buildfarm failure?
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=wasp&dt=2006-04-30%2003
> > > Magnus Hagander wrote:
> > >> Per some earlier discussion, here is an attempt at
> implementing a
> > >> "delayed write" of the pgstats file, to decrease the
> write activity
> > >> on that file.
> >
> > This was not ready to be applied, was it? "An attempt"
> doesn't sound
> > to me
Tom Lane wrote:
> Bruce Momjian writes:
> > Patch applied. Thanks.
>
> > Magnus Hagander wrote:
> >> Per some earlier discussion, here is an attempt at implementing a
> >> "delayed write" of the pgstats file, to decrease the write activity on
> >> that file.
>
> This was not ready to be applied
Bruce Momjian writes:
> Patch applied. Thanks.
> Magnus Hagander wrote:
>> Per some earlier discussion, here is an attempt at implementing a
>> "delayed write" of the pgstats file, to decrease the write activity on
>> that file.
This was not ready to be applied, was it? "An attempt" doesn't so
Patch applied. Thanks.
---
Magnus Hagander wrote:
> Per some earlier discussion, here is an attempt at implementing a
> "delayed write" of the pgstats file, to decrease the write activity on
> that file.
>
> It changes so
> > And it is now also written on backend request. A backend requests a
> > rewrite by simply sending a special stats message. It
> operates on the
> > assumption that the backends aren't actually going to read the
> > statistics file very often, compared to how frequent it's
> written today.
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> And it is now also written on backend request. A backend requests a
> rewrite by simply sending a special stats message. It operates on the
> assumption that the backends aren't actually going to read the
> statistics file very often, compared to how
> > Per some earlier discussion, here is an attempt at implementing a
> > "delayed write" of the pgstats file, to decrease the write
> activity on
> > that file.
> >
> > It changes so the file is only written once every 5 minutes
> > (changeable of course, I just picked something) instead of
Magnus Hagander wrote:
> Per some earlier discussion, here is an attempt at implementing a
> "delayed write" of the pgstats file, to decrease the write activity on
> that file.
>
> It changes so the file is only written once every 5 minutes (changeable
> of course, I just picked something) instead
Per some earlier discussion, here is an attempt at implementing a
"delayed write" of the pgstats file, to decrease the write activity on
that file.
It changes so the file is only written once every 5 minutes (changeable
of course, I just picked something) instead of once every half second.
It's st
17 matches
Mail list logo
