I did it, my pg_log folder was like this:

drwxr-xr-x   2 root     root      4096 Jan 31 09:36 pg_log

Afer I changed to:
drwxr-xr-x   2 postgres postgres  4096 Jan 31 09:36 pg_log

After this I restart the service  (service postgresql restart) ,return to
execute an inaceptble sql statement with this return:

ERROR: insert or update on table "bil" violates foreign key constraint
"fkf97242b3fa73a07c"
SQL state: 23503
Detail: Key (xxx_id)=(20) is not present in table "ctrac".


But the log files doesn't appears on my server.

Any help

Ezequias

2007/1/31, Shoaib Mir <[EMAIL PROTECTED]>:

You need to create the folder manually, give the postgres user permission
for write on it and then restart the database server. This way you should be
able to set the log files in pg_log folder...

------------
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)

On 1/31/07, Ezequias Rodrigues da Rocha < [EMAIL PROTECTED]> wrote:
>
> I restart the server but the pg_log folder doesn't appears.
>
> My log session is like this on postgresql.conf:
>
> # These are only used if redirect_stderr is on:
> log_directory = 'pg_log'        # Directory where log files are written
>                     # Can be absolute or relative to PGDATA
> log_filename = 'postgresql-%Y-%m-%d_%H%M%S.log' # Log file name pattern.
>                     # Can include strftime() escapes
> #log_truncate_on_rotation = off # If on, any existing log file of the
> same
>                     # name as the new log file will be
>                     # truncated rather than appended to. But
>                     # such truncation only occurs on
>                     # time-driven rotation, not on restarts
>                     # or size-driven rotation. Default is
>                     # off, meaning append to existing files
>                     # in all cases.
> #log_rotation_age = 1440        # Automatic rotation of logfiles will
>                     # happen after so many minutes.  0 to
>                     # disable.
> #log_rotation_size = 10240        # Automatic rotation of logfiles will
>                     # happen after so many kilobytes of log
>                     # output.  0 to disable.
>
> Regards...
> Ezequias
>
> 2007/1/31, Ezequias Rodrigues da Rocha < [EMAIL PROTECTED] >:
> >
> > It was commented. Thank you Shoaib Mir
> >
> > I must restart my server ?
> >
> > Ezequias
> >
> > 2007/1/31, Shoaib Mir < [EMAIL PROTECTED]>:
> > >
> > > Check for log_directory setting in your postgresql.conf file...
> > >
> > > -------------
> > > Shoaib Mir
> > > EnterpriseDB (www.enterprisedb.com)
> > >
> > > On 1/31/07, Ezequias Rodrigues da Rocha <[EMAIL PROTECTED]>
> > > 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:
> > > >
> > > > [EMAIL PROTECTED] 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
> > > > [EMAIL PROTECTED] data]#
> > > >
> > > > Can someone tell me how to solve this kind of problem ?
> > > >
> > > >
> > > > Ezequias
> > > > 2007/1/30, Andrew Sullivan <[EMAIL PROTECTED]>:
> > > > > 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  | [EMAIL PROTECTED]
> > > > > 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 [EMAIL PROTECTED] 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/
> >
>
>
>
> --
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>                                   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 via email to