Horton

Re: pg_dump --split patch

Joel Jacobson <joel@gluefinance.com>

View thread
From: Joel Jacobson <joel@gluefinance.com>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Gurjeet Singh <singh.gurjeet@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, Tom Lane <tgl@sss.pgh.pa.us>
Date: 2010-12-28T22:26:06Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. pg_dump: Output functions deterministically sorted

  2. When sorting functions in pg_dump, break ties (same name) by number of arguments

2010/12/28 Andrew Dunstan <andrew@dunslane.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