Re: pgsql: Use TSConfigRelationId in AlterTSConfiguration()

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Use TSConfigRelationId in AlterTSConfiguration()
Date: 2016-12-22 22:20:53
Message-ID: CA+Tgmoad5Jtz_O_aW4b=wPoPTKnYU0As8Mg3xs0beF4ze_KJ5A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

I think that the commit message, especially for something being
back-patched, should try to describe what user-visible problems the
mistake causes, rather than just what was wrong at a code level.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2016-12-22 22:41:37 pgsql: Fix tuple routing in cases where tuple descriptors don't match.
Previous Message Stephen Frost 2016-12-22 22:09:38 pgsql: Use TSConfigRelationId in AlterTSConfiguration()