Re: [HACKERS] Support to COMMENT ON DATABASE CURRENT_DATABASE

From: Jing Wang <jingwangian(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, "Bossart, Nathan" <bossartn(at)amazon(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Surafel Temesgen <surafel3000(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>
Subject: Re: [HACKERS] Support to COMMENT ON DATABASE CURRENT_DATABASE
Date: 2018-01-25 02:15:09
Message-ID: CAF3+xMJaiCeyDsSx=4nYCg5G3BjVR6xgV2=_95O2G3OsR8MQrA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

>Not surprisingly, this patch no longer applies in the wake of commit
>b3f840120. Rather than rebasing the pg_dump portions, I would suggest
>you just drop them.

It has been removed from the pg_dump codes.

>I notice some other patch application failures in dbcommands.c,
>objectaddress.c, and user.c, so there's more work to do besides
>this
Yes. fixed it.

Enclosed please find the latest patch fixed above.

Regards,
Jing Wang
Fujitsu Australia

Attachment Content-Type Size
support_CURRENT_DATABASE_keyword_v4.7.patch application/octet-stream 53.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-01-25 02:49:37 Further cleanup of pg_dump/pg_restore item selection code
Previous Message Amit Langote 2018-01-25 02:11:57 Re: non-bulk inserts and tuple routing