Re: sketchy partcollation handling
Amit Langote <langote_amit_f8@lab.ntt.co.jp>
From: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Amit Langote <amitlangote09@gmail.com>,
"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2017-06-07T00:30:46Z
Lists: pgsql-hackers
On 2017/06/07 0:19, Robert Haas wrote: > On Sun, Jun 4, 2017 at 10:18 PM, Amit Langote > <Langote_Amit_f8@lab.ntt.co.jp> wrote: >> I think we can call it a bug of StorePartitionKey(). I looked at the >> similar code in index_create() (which actually I had originally looked at >> for reference when writing the partitioning code in question) and looks >> like it doesn't store the dependency for collation 0 and for the default >> collation of the database. I think the partitioning code should do the >> same. Attached find a patch for the same (which also updates the >> documentation as mentioned above); with the patch: > > Thanks. Committed. Thank you. Regards, Amit
Commits
-
Fix some cases of "the the" split across two lines.
- 79c4fa0f6229 10.0 landed
-
Clean up partcollation handling for OID 0.
- 2186b608b3cb 10.0 landed