| From: | Gunasekaran Balakrishnan <guna(at)motorola(dot)com> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Test case for bug fix in 7.4.3 |
| Date: | 2004-08-05 03:53:25 |
| Message-ID: | 4111AF35.4080406@motorola.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-08-05 03:59:48 | Re: Test case for bug fix in 7.4.3 |
| Previous Message | Lincoln Yeoh | 2004-08-05 01:49:16 | Re: most idiomatic way to "update or insert"? |