Re: sketchy partcollation handling
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>,
Amit Langote <amitlangote09@gmail.com>,
"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2017-06-06T16:08:50Z
Lists: pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes: > On Sun, Jun 4, 2017 at 10:18 PM, Amit Langote > <Langote_Amit_f8@lab.ntt.co.jp> wrote: >> BTW, the places which check whether the collation to store a dependency >> for is the database default collation don't need to do that. I mean the >> following code block in all of these places: >> >> /* The default collation is pinned, so don't bother recording it */ >> if (OidIsValid(attr->attcollation) && >> attr->attcollation != DEFAULT_COLLATION_OID) > We could go change them all, but I guess I don't particularly see the point. That's an intentional measure to save the catalog activity involved in finding out that the default collation is pinned. It's not *necessary*, sure, but it's a useful and easy optimization. regards, tom lane
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