| From: | Joel Jacobson <joel(at)gluefinance(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: pg_dump --split patch |
| Date: | 2010-12-28 22:26:06 |
| Message-ID: | AANLkTinuDp8OZ5yOg+--iX54YSkN5Pnd-qK-6UEJRAQP@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2010/12/28 Andrew Dunstan <andrew(at)dunslane(dot)net>
>
> I think that's just horrible. Does the i stand for integer or inet? And it
> will get *really* ugly for type names with spaces in them ...
>
>
True, true.
But while "c" is too short, I think "character varying" is too long. Is
there some convenient lookup table to convert between the long names to the
short names?
E.g.,
character varying => varchar
timestamp with time zone => timestamptz
etc.
--
Best regards,
Joel Jacobson
Glue Finance
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-12-28 22:47:13 | Fixing pg_upgrade's check of available binaries |
| Previous Message | Kevin Grittner | 2010-12-28 22:10:59 | SSI SLRU strategy choices |