From: imad <immaad@gmail.com>
To: Ezequias Rodrigues da Rocha <ezequias.rocha@gmail.com>
Cc: Shoaib Mir <shoaibmir@gmail.com>
Cc: Andrew Sullivan <ajs@crankycanuck.ca>
Cc: pgsql-sql@postgresql.org
Subject: Re: Log, Logs and more Logs
Date: Wed, 31 Jan 2007 17:18:27 +0500
Message-ID: <1f30b80c0701310418l711fd82dm957fa7f51d8d0e1@mail.gmail.com> (raw)
In-Reply-To: <55c095e90701310404q64c9e33cgc821268cb8723ac@mail.gmail.com>
References: <55c095e90701300901y41197404q4c26032ff0a28e22@mail.gmail.com>
<20070130172651.GD32170@phlogiston.dyndns.org>
<55c095e90701301041u68c5acc7i99517994724aa6d4@mail.gmail.com>
<20070130213304.GA561@phlogiston.dyndns.org>
<55c095e90701310335x12d824a4q8798638503e45388@mail.gmail.com>
<bf54be870701310339n3413e7b8rd1f6927a0c89dc9e@mail.gmail.com>
<55c095e90701310404q64c9e33cgc821268cb8723ac@mail.gmail.com>
Change it in the postgresql.conf file only if you want to make it permanent.
Otherwise just set the variable for your current session without a
server restart.
--Imad
www.EnterpriseDB.com
On 1/31/07, Ezequias Rodrigues da Rocha <ezequias.rocha@gmail.com> wrote:
> It was commented. Thank you Shoaib Mir
>
> I must restart my server ?
>
> Ezequias
>
> 2007/1/31, Shoaib Mir < shoaibmir@gmail.com>:
> > Check for log_directory setting in your postgresql.conf file...
> >
> > -------------
> > Shoaib Mir
> > EnterpriseDB (www.enterprisedb.com)
> >
> >
> >
> > On 1/31/07, Ezequias Rodrigues da Rocha <ezequias.rocha@gmail.com> wrote:
> > > I noticed today morning that my pg.log doesn't exist in my server.
> > >
> > > Why it occurs ?
> > >
> > > My /var/lib/pgsql/data is like that:
> > >
> > > [root@linux1 data]# ls -la
> > > total 92
> > > drwx------ 10 postgres postgres 4096 Jan 31 08:35 .
> > > drwx------ 4 postgres postgres 4096 Jul 26 2006 ..
> > > drwx------ 7 postgres postgres 4096 Jan 30 12:29 base
> > > drwx------ 2 postgres postgres 4096 Jan 31 08:44 global
> > > drwx------ 2 postgres postgres 4096 Feb 17 2006 pg_clog
> > > -rw------- 1 postgres postgres 3513 Sep 14 15:28 pg_hba.conf
> > > -rw------- 1 postgres postgres 1460 Feb 17 2006 pg_ident.conf
> > > drwx------ 4 postgres postgres 4096 Feb 17 2006 pg_multixact
> > > drwx------ 2 postgres postgres 4096 Jan 28 16:00 pg_subtrans
> > > drwx------ 2 postgres postgres 4096 Feb 17 2006 pg_tblspc
> > > drwx------ 2 postgres postgres 4096 Feb 17 2006 pg_twophase
> > > -rw------- 1 postgres postgres 4 Feb 17 2006 PG_VERSION
> > > drwx------ 3 postgres postgres 4096 Jan 30 13:14 pg_xlog
> > > -rw------- 1 postgres postgres 14079 Jan 30 14:42 postgresql.conf
> > > -rw-r--r-- 1 root root 13652 Mar 17 2006 postgresql.conf.old
> > > -rw------- 1 postgres postgres 49 Jan 31 08:36 postmaster.opts
> > > -rw------- 1 postgres postgres 45 Jan 31 08:36 postmaster.pid
> > > [root@linux1 data]#
> > >
> > > Can someone tell me how to solve this kind of problem ?
> > >
> > >
> > > Ezequias
> > > 2007/1/30, Andrew Sullivan <ajs@crankycanuck.ca>:
> > > > On Tue, Jan 30, 2007 at 04:41:13PM -0200, Ezequias Rodrigues da Rocha
> wrote:
> > > > > So you are tell me that it is impossible to retrieve it ok ?
> > > >
> > > > No.
> > > >
> > > > > Just by changing this values (what I did now) it is possible to get
> > > > > the error messages and their statements OK?.
> > > >
> > > > Yes, but you need to signal the postmaster to reload its config file.
> > > > Either kill -SIGHUP or restart the postmaster. After that, you
> > > > should see the statement that caused your error. Note that if the
> > > > UPDATE itself doesn't cause the error, but say a later COMMIT (you
> > > > can get this in serializable mode easily), you'll see the COMMIT as
> > > > the thing that caused the error.
> > > >
> > > > A
> > > >
> > > > --
> > > > Andrew Sullivan | ajs@crankycanuck.ca
> > > > Unfortunately reformatting the Internet is a little more painful
> > > > than reformatting your hard drive when it gets out of whack.
> > > > --Scott Morris
> > > >
> > > > ---------------------------(end of
> broadcast)---------------------------
> > > > TIP 1: if posting/reading through Usenet, please send an appropriate
> > > > subscribe-nomail command to majordomo@postgresql.org so that
> your
> > > > message can get through to the mailing list cleanly
> > > >
> > >
> > >
> > > --
> > >
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> > > Atenciosamente
> (Sincerely)
> > > Ezequias Rodrigues da Rocha
> > >
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> > > A pior das democracias ainda é melhor do que a melhor das ditaduras
> > > The worst of democracies is still better than the better of
> dictatorships
> > > http://ezequiasrocha.blogspot.com/
> > >
> >
> >
>
>
>
> --
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Atenciosamente
> (Sincerely)
> Ezequias Rodrigues da Rocha
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> A pior das democracias ainda é melhor do que a melhor das ditaduras
> The worst of democracies is still better than the better of dictatorships
> http://ezequiasrocha.blogspot.com/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: immaad@gmail.com, ezequias.rocha@gmail.com, shoaibmir@gmail.com, ajs@crankycanuck.ca
Subject: Re: Log, Logs and more Logs
In-Reply-To: <1f30b80c0701310418l711fd82dm957fa7f51d8d0e1@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox