Re: DDL & DML Logging doesn't work for calling functions - Mailing list pgsql-general

From Albe Laurenz
Subject Re: DDL & DML Logging doesn't work for calling functions
Date
Msg-id D960CB61B694CF459DCFB4B0128514C2072DF6D4@exadv11.host.magwien.gv.at
Whole thread Raw
In response to DDL & DML Logging doesn't work for calling functions  (MURAT KOÇ <m.koc21@gmail.com>)
Responses Re: DDL & DML Logging doesn't work for calling functions
List pgsql-general
MURAT KOÇ wrote:
> Version is PostgreSQL 9.0.4 on x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.1.2 20080704 (Red
> Hat 4.1.2-51), 64-bit.
> 
> We set logging parameters as below for DDL & DML Logging:
> logging_collector = on
> log_statement = mod
> log_line_prefix = '%t--%d--%u--%h--%a--%i--%e'

> Logging works successfully while we run direct DML commands like "insert, update, delete".
> 
> But, when I call a function that does DML, logging doesn't work and server log file has no information
> about calling function.
> 
> I call function like this: SELECT p_dummy_insert();
> 
> ###This is sample insert function###
> CREATE OR REPLACE FUNCTION p_dummy_insert ()
>   RETURNS void AS
> $BODY$
> BEGIN
>  INSERT INTO employee values ('dummy', 'test');
> END$BODY$
>   LANGUAGE plpgsql VOLATILE
>   COST 100;
> 
> "Not logging of function calls" is expected behavior or a bug? We have no information on server logs
> about who called function or when was it called or what did called function do?

The function call itself is logged, but SQL statements inside
the function are not.

The function call does not show up in your log because it is
in a SELECT statement.

Set log_statement = 'all' to log the function call.

Yours,
Laurenz Albe

pgsql-general by date:

Previous
From: "Albe Laurenz"
Date:
Subject: Re: odbc_fdw
Next
From: Venkat Balaji
Date:
Subject: : pg_compresslog (pglesslog)