[REL6.4] Mixed case table name problems with some fixes.

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

Your name : Billy G. Allie
Your email address : Bill(dot)Allie(at)mug(dot)org

System Configuration
---------------------
Architecture (example: Intel Pentium) : Intel 486DX2

Operating System (example: Linux 2.0.26 ELF) : UnixWare 7.0

PostgreSQL version (example: PostgreSQL-6.4) : PostgreSQL-6.4

Compiler used (example: gcc 2.8.0) : Optimizing C Compilation System
(CCS) 3.2 08/18/98 (u701)

Please enter a FULL description of your problem:
------------------------------------------------
There are a number of problems with using mixed case table names:

1. Using constraints on tables whose name contains mixed case will fail.

2. Creating triggers on tables whose name contains mixed case will fail.

3. In pgsql, the command '\d *' will fail.

Please describe a way to repeat the problem. Please try to provide a
concise reproducible example, if at all possible:
----------------------------------------------------------------------
1. Create a table that has a mixed case name and a constraint such as
a default or a primary key.

2. Create a trigger on a table with a mixed case name.

3. In psql, execute the '\d *' command in a database that has tables
mixed case names.

If you know how this problem might be fixed, list the solution below:
---------------------------------------------------------------------
The following patch file fixes problems 1 and 3. Thomas G. Lockhart's
patch to fix problem 1 was incomplete. I added the additional changes
to 'heap.c' that were needed to complete the fix.