Re: Logging SQL queries?

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Phil Geer <philg(at)gearcc(dot)com>
Cc: Steve Lane <slane(at)fmpro(dot)com>, pgsql <pgsql-general(at)postgresql(dot)org>
Subject: Re: Logging SQL queries?
Date: 2002-07-17 08:32:44
Message-ID: Pine.LNX.4.44.0207170132330.30489-100000@crazypenguins.commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


You can use the -d option with your start script

On Wed, 17 Jul 2002, Phil Geer wrote:

> SET DEBUG_PRINT_QUERY TO 1
> it might be
> SET DEBUG_PRINT_QUERY TO ON
>
> Had to do this a couple weeks back to debug something.
>
> That should work it'll print your queries to the standard log file but the
> experts may have a way to get it into another file for you.
>
> Good Luck
> Phil
> ----- Original Message -----
> From: "Steve Lane" <slane(at)fmpro(dot)com>
> To: "PostgreSQL General Mailing List" <pgsql-general(at)postgresql(dot)org>
> Sent: Tuesday, July 16, 2002 11:40 PM
> Subject: [GENERAL] Logging SQL queries?
>
>
> > Hello all:
> >
> > I want to do some profiling of a large application I run under postgres.
> > Ideally I'd like to capture just the queries that are submitted to the
> > database. It would be rather annoying to have to log them from the
> > application layer, so I'm hoping there's some suitable log-level setting
> on
> > the back end that can do this. Something that could log only the queries
> to
> > a different specific file would be excellent, but any flavor of this would
> > be good.
> >
> > Thanks,
> >
> > steve
> >
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 4: Don't 'kill -9' the postmaster
> >
> >
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Joshua D. Drake 2002-07-17 08:34:08 Re: Securing PostgreSQL
Previous Message Joshua D. Drake 2002-07-17 08:32:10 Re: Question: merit / feasibility of compressing frontend