On Wednesday 20 May 2009 11:36:38 pm Moshe Ben-Shoham wrote:
> Hi,
>
>
>
> We're working with version 8.3.5-1.
>
>
>
> Lately we started seeing insert statements hang in the DB. The
> statements come from two different clients.
>
>
>
> When it happens, I see the following messages in the log every second or
> so:
>
>
>
> 2009-05-21 08:56:49 IDT ERROR: permission denied to set parameter
> "log_statement"
>
> 2009-05-21 08:56:49 IDT STATEMENT: SET log_statement='none';
>
> 2009-05-21 08:56:50 IDT ERROR: permission denied to set parameter
> "log_statement"
>
> 2009-05-21 08:56:50 IDT STATEMENT: SET log_statement='none';
>
> 2009-05-21 08:56:51 IDT ERROR: permission denied to set parameter
> "log_statement"
>
> 2009-05-21 08:56:51 IDT STATEMENT: SET log_statement='none';
>
> 2009-05-21 08:56:52 IDT ERROR: permission denied to set parameter
> "log_statement"
>
> 2009-05-21 08:56:52 IDT STATEMENT: SET log_statement='none';
>
> 2009-05-21 08:56:53 IDT ERROR: permission denied to set parameter
> "log_statement"
>
> 2009-05-21 08:56:53 IDT STATEMENT: SET log_statement='none';
>
> 2009-05-21 08:56:54 IDT ERROR: permission denied to set parameter
> "log_statement"
>
> 2009-05-21 08:56:54 IDT STATEMENT: SET log_statement='none';
>
> 2009-05-21 08:56:55 IDT ERROR: permission denied to set parameter
> "log_statement"
>
> 2009-05-21 08:56:55 IDT STATEMENT: SET log_statement='none';
>
>
>
> Any help (or guidelines for additional required information) is
> appreciated.
>
>
>
> Thanks,
>
> Moshe.
>
>
Would seem that the insert statements are being done in conjunction with the SET
log_statement and that the client(s) doing that do not have the necessary
permission level to set log_statement.
--
Adrian Klaver
aklaver@comcast.net