| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Joel Jacobson <joel(at)gluefinance(dot)com>, Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump --split patch |
| Date: | 2010-12-28 22:51:23 |
| Message-ID: | 11551.1293576683@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 12/28/2010 04:44 PM, Joel Jacobson wrote:
>> Perhaps abbreviations are to prefer, e.g., myfunc_i, myfunc_i_c, etc
>> to reduce the need of truncating filenames.
> 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 ...
You think spaces are bad, try slashes ;-)
Not to mention the need for including schemas in typenames sometimes.
I think you're going to have a real problem trying to fully describe a
function's signature in a file name of reasonable max length.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gurjeet Singh | 2010-12-28 22:55:48 | Re: pg_dump --split patch |
| Previous Message | Tom Lane | 2010-12-28 22:47:13 | Fixing pg_upgrade's check of available binaries |