From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Robert Haas <rhaas(at)postgresql(dot)org> |
Cc: | pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Unbreak legacy syntax "COMMENT ON RULE x IS y", with no relation |
Date: | 2011-08-11 15:36:10 |
Message-ID: | CA+TgmoYKmj0sY4VrnFbMgs6FyAGTRXEc4v9Z++8sc4-Qd4AZ4Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On Thu, Aug 11, 2011 at 11:29 AM, Robert Haas <rhaas(at)postgresql(dot)org> wrote:
> Unbreak legacy syntax "COMMENT ON RULE x IS y", with no relation name.
>
> check_object_ownership() isn't happy about the null relation pointer.
> We could fix it there, but this seems more future-proof.
>
> Branch
> ------
> REL9_1_STABLE
>
> Details
> -------
> http://git.postgresql.org/pg/commitdiff/a60c16db5f36562df571d36fcacbbed33fd40bd4
>
> Modified Files
> --------------
> src/backend/catalog/objectaddress.c | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
Woops. This was a live bug only on the master branch. I mistakenly
thought 9.1 had the same issue, but it turns out to have been
introduced by commit c533c1477f6beede766034c1226a20ac08320b05. I
didn't notice that the rebase over 9.1 worked out to only a comment
change.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-08-11 15:47:19 | pgsql: Display both per-table and per-column FDW options in psql's \d o |
Previous Message | Robert Haas | 2011-08-11 15:29:40 | pgsql: Unbreak legacy syntax "COMMENT ON RULE x IS y", with no relation |