Skip site navigation (1) Skip section navigation (2)

Re: pg_dump --split patch

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: (view raw, whole thread or download thread mbox)
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

In response to


pgsql-hackers by date

Next:From: Gurjeet SinghDate: 2010-12-28 22:55:48
Subject: Re: pg_dump --split patch
Previous:From: Tom LaneDate: 2010-12-28 22:47:13
Subject: Fixing pg_upgrade's check of available binaries

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group