The oidvectortypes function, mostly used by psql \df, formats types
separated by spaces:

	varchar float8 timetz int4

which would look a little odd when canonical type names are used:

	character varying double precision time with time zone integer

I suggest that we separate the types by <comma><space>, which also looks a
little more like how they are invoked in a function call.

Concerns?


-- 
Peter Eisentraut                  Sernanders vï¿½g 10:115
peter_e@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden


Fri, 7 Jul 2000 21:26:56 +0200 (CEST)
Peter Eisentraut <peter_e@gmx.net>
Type formatting and oidvectortypes
Peter Eisentraut <peter_e@gmx.net> writes:
> I suggest that we separate the types by <comma><space>, which also looks a
> little more like how they are invoked in a function call.

No strong objections here.  I'm not very concerned about backwards
compatibility because there probably aren't many apps besides psql
that use oidvectortypes at all.  (Heck, we renamed the function in
7.0, and I don't recall many complaints...)

			regards, tom lane

Fri, 07 Jul 2000 19:22:45 -0400
Tom Lane <tgl@sss.pgh.pa.us>
Re: Type formatting and oidvectortypes 