Look in postgresql.conf file:
#
# Message display
#
server_min_messages = info # Values, in order of decreasing detail:
# debug5, debug4, debug3, debug2, debug1,
# info, notice, warning, error, log, fatal,
# panic
client_min_messages = info # Values, in order of decreasing detail:
# debug5, debug4, debug3, debug2, debug1,
# log, info, notice, warning, error
#silent_mode = false
log_connections = true
#log_pid = false
log_statement = true
log_duration = true
log_timestamp = true
These are the main log settings. After you modify this data's reload the
configuration files. (pg_ctl ... reload).
Best r.
Andy.
----- Original Message -----
From: "Peter Childs" <blue.dragon@blueyonder.co.uk>
Cc: <pgsql-admin@postgresql.org>
Sent: Thursday, December 04, 2003 12:26 PM
Subject: Re: [ADMIN] see previous queries
>
>
> On Thu, 4 Dec 2003, Sai Hertz And Control Systems wrote:
>
> >
> > Dear Ashok,
> >
> > Hope you are not using
> > Postgresql 7.4
> > if this is the case I think some insert /update statements are waiting
> > for commit command
> >
> > Regards,
> > V Kashyap
> >
> > >hi
> > >i am a new user in postgresql.
> > >problem:- in postgresql there is any command to see history (previous
> > >day queries) like as history command in linux.
> > >thank you
> > >
>
> postgres will log your queries. You need to configure it to do so.
> 7.4 also logs queries that take a long time. The logs go either to file or
> the system message log. depending on how you set it up in postgresql.conf.
> The log can not be used to rebuild your database :(
> psql also has a shell like history function.
>
> Peter Childs
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
