-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday 08 June 2001 12:26, Peter Eisentraut wrote:
> Seems like the two installations are running under different locales.
> Since you didn't give much information I can only guess that the "old
> version" is prior to 7.1 and running in some non-C locale, whereas the
> "new version" is 7.1 or later but was initialized in the C locale. Note
> that 7.1 or later always use the locale at initdb time for sort order.
He specified the _new_ installation as Red Hat 7.1, with PostgreSQL 7.0.3 --
which has no 'hard-wiring' to a C locale for initdb.
If it were an upgrade, it would have just about had to have been from 6.4.2
or earlier -- although it is slimly possible it could be a 6.5.x prior,
unless he had 7.0.x running on a Red Hat <7.0, which would just about have to
be either a machine at RH 6.0, or a machine that has been upgraded from RH
6.0 to RH 6.1 or 2.
I base that on the fact the the collation change was a Red Hat 6.1 and later
deal -- and Red Hat 6.1 shipped PostgreSQL 6.5.2. Red Hat 6.0 shipped
PostgreSQL 6.4.2, RH 5.1 and 5.2 shipped PG6.3.2, and RH 5.0 shipped PG
6.2.1. RH 7.0 shipped PG 7.0.2. Also, an upgrade from RH 6.0 to either 6.1
or 6.2 doesn't force the i18n issue -- but, IIRC, an upgrade from 6.0 to 7.x
_does_.
- --
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7IRpA5kGGI8vV9eERApdzAJ9MqqVB5EOhRJpqND/S1esE+Eu+UQCgkzvF
dBDVZHqXqVl1s67xLUXBfS0=
=Dvr4
-----END PGP SIGNATURE-----