Re: BUG #11350: ALTER SYSTEM is not DDL?

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: 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 19:14:56
Message-ID: 20140904191456.GW16422@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

* 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...

Thanks,

Stephen

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2014-09-04 20:12:48 Re: BUG #11350: ALTER SYSTEM is not DDL?
Previous Message Fujii Masao 2014-09-04 17:33:48 Re: BUG #11335: an invalid prepare statement causes crash at log_statement = 'mod' or 'ddl'.