pgsql: Clean up partcollation handling for OID 0.

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Clean up partcollation handling for OID 0.
Date: 2017-06-06 15:18:22
Message-ID: E1dIGFS-0002iR-F0@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Clean up partcollation handling for OID 0.

Consistent with what we do for indexes, we shouldn't try to record
dependencies on collation OID 0 or the default collation OID (which
is pinned). Also, the fact that indcollation and partcollation can
contain zero OIDs when the data type is not collatable should be
documented.

Amit Langote, per a complaint from me.

Discussion: http://postgr.es/m/CA+Tgmoba5mtPgM3NKfG06vv8na5gGbVOj0h4zvivXQwLw8wXXQ@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/2186b608b3cb859fe0ec04015a5c4e4cbf69caed

Modified Files
--------------
doc/src/sgml/catalogs.sgml | 6 ++++--
src/backend/catalog/heap.c | 11 ++++++++---
2 files changed, 12 insertions(+), 5 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2017-06-06 15:22:01 pgsql: Use NIL rather than NULL to represent an empty list.
Previous Message Michael Meskes 2017-06-06 10:20:48 pgsql: Fix docs to not claim ECPG's SET CONNECTION is not thread-aware.