General Bug Report: INSTALL and regression notes

============================================================================
POSTGRESQL BUG REPORT TEMPLATE
============================================================================

Your name : Michael Van Biesbrouck
Your email address : mlvanbie(at)thinkage(dot)on(dot)ca

Category : install: other
Severity : non-critical

Summary: INSTALL and regression notes

System Configuration
--------------------
Operating System : Linux 2.2.1 libc 5.4.44

PostgreSQL version : 6.5

Compiler used : gcc 2.7.2

Hardware:
---------
Linux valium 2.2.1 #4 Sat Feb 6 20:20:13 EST 1999 i586
AMD K6, 96MB RAM (was Slackware once upon a time)

Versions of other tools:
------------------------
GNU make, flex, etc.

--------------------------------------------------------------------------

Problem Description:
--------------------
1. LC_COLLATE appears twice:

LC_COLLATE=C
LC_CTYPE=C
LC_COLLATE=C
export LC_COLLATE LC_CTYPE LC_COLLATE

2. User told to add a lib directory owned by an insecure
userid (postgress) to ld.so.conf.

3. int2 and int4 test produce
ERROR: pg_atoi: error reading "100000": Math result not representable
instead of
ERROR: pg_atoi: error reading "100000": Numerical result out of range

4. horology regression test: I get PST instead of PDT and
-08 as a timezone instead of -07 on many lines. Am I
broken?

--------------------------------------------------------------------------

Test Case:
----------

--------------------------------------------------------------------------

Solution:
---------
1. One of these should be LC_LANG?
2. The lib directory should be put at the end to prevent
people from breaking into the PostgreSQL account and
replacing libc.so. Different arrangements might be
required on different machines and this might not
succeed if a program looks for a particular libc version
that hasn't been install.

On systems that support it, the -rpath options should
be used when building executables so that they know
where to find their libraries. See the Perl 5 build
scripts to find out how to do this on different machines.

3. Either put a FAQ entry or determine which libc versions
give this message and provide alternate expected files.

4. Not sure.

--------------------------------------------------------------------------