BUG #11350: ALTER SYSTEM is not DDL?

From: katsumata(dot)tomonari(at)po(dot)ntts(dot)co(dot)jp
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #11350: ALTER SYSTEM is not DDL?
Date: 2014-09-04 05:13:56
Message-ID: 20140904051356.2926.42797@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 11350
Logged by: Tomonari Katsumata
Email address: katsumata(dot)tomonari(at)po(dot)ntts(dot)co(dot)jp
PostgreSQL version: 9.4beta2
Operating system: RHEL6.4 x86_64
Description:

Hi,

I found an odd thing about logging for alter system.

When I set 'log_statement=ddl' and execute ALTER SYSTEM,
any log messages are not outputted.

-----------------------------------------------
[log_statement = ddl]
postgres=# alter system set autovacuum to off;
ALTER SYSTEM
-----------------------------------------------

Whereas, when I set 'log_statemnt = all' then log messege is outputted.

-----------------------------------------------
[log_statement = all]
postgres=# alter system set autovacuum to off;
LOG: statement: alter system set autovacuum to off;
ALTER SYSTEM
-----------------------------------------------

The document says about log_statement:
>ddl logs all data definition statements, such as CREATE, ALTER, and DROP
statements.

So I think log message should be outputted when executing ALTER SYSTEM with
'log_statement = ddl'.

Am I missing something?

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Amit Kapila 2014-09-04 06:38:14 Re: BUG #11350: ALTER SYSTEM is not DDL?
Previous Message Joe Van Dyk 2014-09-03 22:43:31 Re: postgres randomly gets into state where it returns hstore as string