pgsql: Clarify comments in enforce_generic_type_consistency().

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Clarify comments in enforce_generic_type_consistency().
Date: 2020-09-07 18:52:42
Message-ID: E1kFMFu-0003g8-LX@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Clarify comments in enforce_generic_type_consistency().

Some of the pre-existing comments were vague about whether they
referred to all polymorphic types or only the old-style ones.

Also be more consistent about using the "family 1" vs "family 2"
terminology.

Himanshu Upadhyaya and Tom Lane

Discussion: https://postgr.es/m/CAPF61jBUg9XoMPNuLpoZ+h6UZ2VxKdNt3rQL1xw1GOBwjWzAXQ@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/53367e6c62e3111eccdd578a3fa607c48c3e1fb6

Modified Files
--------------
src/backend/parser/parse_coerce.c | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Jeff Davis 2020-09-07 20:39:56 pgsql: Adjust cost model for HashAgg that spills to disk.
Previous Message Tom Lane 2020-09-07 17:58:40 Re: pgsql: Refactor pg_get_line() to expose an alternative StringInfo-based