From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Can pg_dump make use of CURRENT/SESSION_USER |
Date: | 2015-08-25 13:01:51 |
Message-ID: | CAB7nPqRE=EfoxNRwHayM2NWz-dLXcmom3PH2LOVbPAYikaBMdA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Apr 30, 2015 at 2:04 AM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Fabrízio de Royes Mello wrote:
>
>> I have this idea:
>>
>> 1) Add an ObjectAddress field to CommentStmt struct an set it in gram.y
>>
>> 2) In the CommentObject check if CommentStmt->address is
>> InvalidObjectAddress then call get_object_address else use it
>
> For DDL deparsing purposes, it seems important that the affected object
> address can be reproduced somehow. I think pg_get_object_address()
> should be considered, as well as the object_address test.
>
> If we do as you propose, we would have to deparse
> COMMENT ON CURRENT DATABASE IS 'foo'
> as
> COMMENT ON DATABASE whatever_the_name_is IS 'foo'
>
> which is not a fatal objection but doesn't seem all that great.
Seeing no activity in the last couple of months for this patch that
had reviews, it is now marked as returned with feedback.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2015-08-25 13:03:33 | Re: Improving replay of XLOG_BTREE_VACUUM records |
Previous Message | Andrew Dunstan | 2015-08-25 12:57:11 | Re: 9.4 broken on alpha |