From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: DDL support for collations |
Date: | 2011-02-12 16:54:46 |
Message-ID: | 4108.1297529686@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> DDL support for collations
When you are adding a new DumpableObject type to pg_dump, please do NOT
do this:
@@ -95,7 +96,8 @@ static const int newObjectTypePriority[] =
16, /* DO_FOREIGN_SERVER */
28, /* DO_DEFAULT_ACL */
20, /* DO_BLOB */
- 22 /* DO_BLOB_DATA */
+ 22, /* DO_BLOB_DATA */
+ 3 /* DO_COLLATION */
};
That is, do not just give the new object type the same sort priority as
some randomly-chosen existing type. The effect of what you've done is
that collations and extensions will be intermixed in the dump output,
which is ugly. Give collations their own place in the sort order and
renumber the existing entries as necessary to support that.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-02-12 17:03:22 | Re: pgsql: Properly handle Win32 paths of 'E:abc', which can be either abso |
Previous Message | Bruce Momjian | 2011-02-12 14:48:22 | pgsql: Properly handle Win32 paths of 'E:abc', which can be either abso |