From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, katsumata(dot)tomonari(at)po(dot)ntts(dot)co(dot)jp, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #11350: ALTER SYSTEM is not DDL? |
Date: | 2014-09-04 20:12:48 |
Message-ID: | 20140904201248.GE3625@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 2014-09-04 15:14:56 -0400, Stephen Frost wrote:
> * Amit Kapila (amit(dot)kapila16(at)gmail(dot)com) wrote:
> > On Thu, Sep 4, 2014 at 10:43 AM, <katsumata(dot)tomonari(at)po(dot)ntts(dot)co(dot)jp> wrote:
> > > So I think log message should be outputted when executing ALTER SYSTEM
> > with
> > > 'log_statement = ddl'.
> > >
> > > Am I missing something?
> >
> > Currently it is considered similar to SET statement as it performs
> > similar operation except that the value for configuration gets set
> > in configuration file. Do you see any reason for it to be considered
> > differently except that the command has ALTER keyword?
>
> Uh, it's nothing like SET as SET only affects the current session.
>
> It's much, much closer to ALTER ROLE, which correctly logs at the DDL
> level. This should be fixed, and before 9.4 goes out...
+1.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tomonari Katsumata | 2014-09-05 01:30:34 | Re: BUG #11350: ALTER SYSTEM is not DDL? |
Previous Message | Stephen Frost | 2014-09-04 19:14:56 | Re: BUG #11350: ALTER SYSTEM is not DDL? |