Hi, again.
I've turned on only log_connections and log_statement. See the following
log fragment (I've included lines only related to opening of new
connection);
Nov 21 11:06:44 postgres[3359]: [3-1] LOG: connection received: host= port=
Nov 21 11:06:44 postgres[3359]: [4-1] LOG: connection au
Ryszard Lach <[EMAIL PROTECTED]> writes:
> It seems, that empty statements are generated during opening of
> connection.
Hmm. Try asking about that on the pgsql-jdbc list. I think the JDBC
driver must actually be sending empty commands.
Looking at the backend code, I realize that 7.4 will emit
On Thu, Nov 20, 2003 at 07:17:01PM -0500, Tom Lane wrote:
>
>
> Is it possible that you're sending a lot of queries that have an initial
> newline in the text? I'd expect the first line of log output for such a
> query to look as above.
I don't think so, but it is possible, that queries have e.
Ryszard Lach <[EMAIL PROTECTED]> writes:
> Nov 18 10:05:20 postgres[1348]: [318-1] LOG: duration: 0.297 ms statement:
> Nov 18 10:05:20 postgres[1311]: [5477-1] LOG: duration: 0.617 ms statement:
> Nov 18 10:05:20 postgres[1312]: [5134-1] LOG: duration: 0.477 ms statement:
> Nov 18 10:05:2
Ryszard Lach wrote:
> On Wed, Nov 19, 2003 at 01:58:27PM -0500, Bruce Momjian wrote:
> > Ryszard Lach wrote:
> >
> > > There is another one thing: logs from the same database running on 7.3 and the
> > > same
> > > application contained lines like 'select getdatabaseencoding()', 'select
> > > dat
On Wed, Nov 19, 2003 at 01:58:27PM -0500, Bruce Momjian wrote:
> Ryszard Lach wrote:
>
> > There is another one thing: logs from the same database running on 7.3 and the same
> > application contained lines like 'select getdatabaseencoding()', 'select
> > datestyle()' and similar (not used by appl
On Tue, Nov 18, 2003 at 10:07:48AM -0500, Bruce Momjian wrote:
>
> Wow, that is strange. If you don't use syslog, do you see the proper
> output?
I've just checked this. It behaves exactly the same way.
> If you turn on log_statement, do you see the statements?
If I turn on log_min_duration_s
Ryszard Lach wrote:
> If I turn on log_min_duration_statement (i.e. set to 0), log_statement and
> log_duration, then I receive something like that
>
> Nov 17 22:33:27 postgres[22945]: [29231-1] LOG: statement:
> Nov 17 22:33:27 postgres[22945]: [29232-1] LOG: duration: 0.198 ms
> Nov 17 22:33:2
Wow, that is strange. If you don't use syslog, do you see the proper
output? If you turn on log_statement, do you see the statements?
---
Ryszard Lach wrote:
> On Mon, Nov 17, 2003 at 09:37:07PM -0500, Bruce Momjian wrote:
On Mon, Nov 17, 2003 at 09:37:07PM -0500, Bruce Momjian wrote:
> Ryszard Lach wrote:
> >
> > Hi.
> >
> > I'm trying to set run-time environment in pgsql7.4 so, that it prints
> > all statements with duration time, but I can't understand why setting
> > log_min_duration_statement to '0' causes pri
Ryszard Lach wrote:
>
> Hi.
>
> I'm trying to set run-time environment in pgsql7.4 so, that it prints
> all statements with duration time, but I can't understand why setting
> log_min_duration_statement to '0' causes printing to syslog plenty of
> lines ending with 'duration: statement:', i.e. wi
Hi.
I'm trying to set run-time environment in pgsql7.4 so, that it prints
all statements with duration time, but I can't understand why setting
log_min_duration_statement to '0' causes printing to syslog plenty of
lines ending with 'duration: statement:', i.e. without any statement
string (except
12 matches
Mail list logo
