Обсуждение: Re: Test case for bug fix in 7.4.3

The problem is that postgres is distributed as part of our product.
The last release we did was a month ago, where we upgraded from
7.2.2 to 7.4.2. There is no scheduled upgrade for the next 6 months.
So, I want to see how critical this problem is and what the chances
are of this occuring on our customer sites.

Thanks,
guna.



Bruce Momjian wrote:

Gunasekaran Balakrishnan wrote: 

Hi,
    I see that one of the bug fixes in 7.4.3 is:

"Fix temporary memory leak when using non-hashed aggregates (Tom)"

I am still using 7.4.2, and want to find out if I need to upgrade to 7.4.3.

I did not quite understand the bug, or find a way to re-produce this in the
mailist archives.

Can someone point me to the test case which can re-produce this problem.   

No, just upgrade, it is very easy, just stop, install, restart.
 

Gunasekaran Balakrishnan wrote:
> The problem is that postgres is distributed as part of our product.
> The last release we did was a month ago, where we upgraded from
> 7.2.2 to 7.4.2. There is no scheduled upgrade for the next 6 months.
> So, I want to see how critical this problem is and what the chances
> are of this occuring on our customer sites.
>
> Thanks,
> guna.
>
>
>
> Bruce Momjian wrote:
>
> >Gunasekaran Balakrishnan wrote:
> >
> >
> >>Hi,
> >>
> >>     I see that one of the bug fixes in 7.4.3 is:
> >>
> >>"Fix temporary memory leak when using non-hashed aggregates (Tom)"
> >>
> >>I am still using 7.4.2, and want to find out if I need to upgrade to 7.4.3.
> >>
> >>I did not quite understand the bug, or find a way to re-produce this in the
> >>mailist archives.
> >>
> >>Can someone point me to the test case which can re-produce this problem.
> >>
> >>
> >
> >No, just upgrade, it is very easy, just stop, install, restart.

Ah, that is a tricky one.  I don't think the problem is serious enough
to cause a mass upgrade.  As I remember, the issue is that larger
aggregates could run out of memory and the query would fail.  The memory
is always reclaimed at the end of the statement so unless you are seeing
aggregate failures, you should be fine.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

I would like to point out that NOT applying the latest sub minor
upgrades is a very bad idea.  revisions that cause a bump in the third
number of postgresql are always and only bug fixes.  Unlike many other
projects, I've found there to be no real liability to upgrading to the
latest sub rev of postgresql.  While many of the bugs are minor,
occasionally some aren't, and missing a bug fix revision is a good way
to get bitten by one.

On Wed, 2004-08-04 at 21:53, Gunasekaran Balakrishnan wrote:
> The problem is that postgres is distributed as part of our product.
> The last release we did was a month ago, where we upgraded from
> 7.2.2 to 7.4.2. There is no scheduled upgrade for the next 6 months.
> So, I want to see how critical this problem is and what the chances
> are of this occuring on our customer sites.
>
> Thanks,
> guna.
>
>
>
> Bruce Momjian wrote:
> > Gunasekaran Balakrishnan wrote:
> >
> > > Hi,
> > >
> > >      I see that one of the bug fixes in 7.4.3 is:
> > >
> > > "Fix temporary memory leak when using non-hashed aggregates (Tom)"
> > >
> > > I am still using 7.4.2, and want to find out if I need to upgrade to 7.4.3.
> > >
> > > I did not quite understand the bug, or find a way to re-produce this in the
> > > mailist archives.
> > >
> > > Can someone point me to the test case which can re-produce this problem.
> > >
> > No, just upgrade, it is very easy, just stop, install, restart.
> >
> >
>