| From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>, Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | pgsql-sql(at)hub(dot)org, "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] pg_dump bug (was Re: [SQL] Slow Inserts Again) |
| Date: | 1999-05-04 13:54:33 |
| Message-ID: | 372EFC19.7A9E6514@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
> ... pg_dump seems to have problems with mixed case tablenames. There
> doesn't seem to be a way to send a quoted tablename into pg_dump as the
> value for a -t option, in 6.4.2 (example below). Can someone try this on
> 6.5beta? I know some issues with quoting output of pg_dump (i.e. COPY)
> was addressed, I'm wondering if input parsing got touched.
pg_dump explicitly converts all table names to lowercase. I've got a
patch which looks for a table name which starts with a double quote,
and suppresses the case conversion if so:
[postgres(at)golem pg_dump]$ pg_dump -t '"MixedCase"' postgres
CREATE TABLE "MixedCase" (
"i" int4);
COPY "MixedCase" FROM stdin;
1
2
\.
Patch enclosed for you to try. Bruce, any reason not to apply this to
the tree?
- Tom
--
Thomas Lockhart lockhart(at)alumni(dot)caltech(dot)edu
South Pasadena, California
| Attachment | Content-Type | Size |
|---|---|---|
| pg_dump.c.patch | text/plain | 1.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 1999-05-04 14:04:10 | Re: [HACKERS] an older problem? hash table out of memory |
| Previous Message | Tom Lane | 1999-05-04 13:51:45 | varchar-array.patch applied |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1999-05-04 16:55:40 | Re: [HACKERS] pg_dump bug (was Re: [SQL] Slow Inserts Again) |
| Previous Message | Ingrith Andrea Correa Vargas | 1999-05-04 13:27:23 | inheritance |