| From: | Дмитрий Воронин <carriingfate92(at)yandex(dot)ru> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump |
| Date: | 2015-10-29 14:05:02 |
| Message-ID: | 665091446127502@web10o.yandex.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> It's a problem. See this recent discussion:
> http://www.postgresql.org/message-id/flat/20150710115735(dot)GH26521(at)alap3(dot)anarazel(dot)de
Postgresmen, we have a SQL function "current_database", which can be called by statement "SELECT CURRENT_CATALOG".
If we will use CURRENT_CATALOG keyword, we can update syntax of COMMENT statement:
COMMENT ON DATABASE CURRENT_CATALOG IS 'comment';
And pg_dump will create this line for database. What are you think about this idea? Later, I send a patch with it.
P.S. Maybe we can apply this mechanism for dumping SECURITY LABEL statetment.
--
Best regards, Dmitry Voronin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2015-10-29 14:16:32 | Re: Support for N synchronous standby servers - take 2 |
| Previous Message | Tom Lane | 2015-10-29 13:50:27 | Re: psql: add \pset true/false |