Test case for bug fix in 7.4.3 - Mailing list pgsql-general

From Gunasekaran Balakrishnan
Subject Test case for bug fix in 7.4.3
Date
Msg-id 4110A39A.8050900@motorola.com
Whole thread Raw
In response to DIfferent ORDER BY behaviour in 7.4.2  (Gunasekaran Balakrishnan <guna@motorola.com>)
Responses Re: Test case for bug fix in 7.4.3  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-general
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.

Thanks a lot in advance,
guna.



Gunasekaran Balakrishnan wrote:
Thanks a lot Tom !!
Locale settings was the problem.

Thanks,
guna.


Tom Lane wrote:
Gunasekaran Balakrishnan <guna@motorola.com> writes: 
     I am seeing a different sorting behaviour for varchar columns in
Postgres 7.4.2.
postgres 7.4.2 is ignoring case for varchar columns for "ORDER BY"
commands where as 7.2.2 is not.   
Check your locale settings.
IIRC, --enable-locale was not default in 7.2 days, but it is default
(in fact mandatory) now.  So it's possible that the 7.2 installation
doesn't have locale support at all and is defaulting to C-locale
behavior.  If your 7.2 was built with locale support, then it was
probably initdb'd under a different locale setting than your 7.4 was.
In 7.4 you can just do "show lc_collate" to check, but in 7.2 I think
you have to use pg_controldata (or in a pinch, "strings pg_control")
to find out what locale it's using.		regards, tom lane 


pgsql-general by date:

Previous
From: Pierre-Frédéric Caillaud
Date:
Subject: Re: Casting timestamp with time zone to varchar automatically
Next
From: Bernd Helmle
Date:
Subject: Re: Updateable Views?