Обсуждение: DB problem

Поиск
Список
Период
Сортировка

DB problem

От
vinayakr@vmoksha.com
Дата:
<font face="Default Sans Serif, Verdana, Arial, Helvetica, sans-serif" size="2"><div><div><font face="Default Sans
Serif,Verdana, Arial, Helvetica, sans-serif" size="2"><div>Hi,</div><div> </div><div>We are using PostgreSQL 7.3
version,installed in linux system. Only DB is getting shut down 3-4 times a day. From my application end I get "Sorry
toomany clients" error. <br />Refering the FAQ I maximized the DB session limit to 200. </div><div> </div><div>I think
thelogs are not enabled in my DB. So I set the following options in postgresql.con file<br /> <br />log_timestamp=
true<br/>log_directory=pg_log              <br />log_filename=%Y-%m-%d_%H%M%S.log      <br
/>log_disconnections=true    <br />log_hostname=true   
</div><div>log_statement=true</div><div> </div><div> </div><div>After restartingthe system got the following error :
</div><div>[root@localhostroot]# su postgres bash-2.05b$ postmaster -i -D /var/lib/pgsql/data FATAL:
postgresql.conf:131:syntax error, <br />token="%" bash-2.05b$ postmaster -i -D /var/lib/pgsql/data FATAL:
postgresql.conf:131:syntax error, token="%" bash-2.05b$ postmaster -i -D /var/lib/pgsql/data FATAL:
postgresql.conf:131:syntax error, token="%" bash-2.05b$ postmaster -i -D /var/lib/pgsql/data FATAL: 'log_directory' is
nota valid option name bash-2.05b$ postmaster -i -D /var/lib/pgsql/data FATAL: 'log_directory' is not a valid option
namebash-2.05b$ postmaster -i -D /var/lib/pgsql/data FATAL: 'log_filename' is not a valid option name bash-2.05b$
postmaster-i -D /var/lib/pgsql/data FATAL: 'log_disconnections' is not a valid option name bash-2.05b$ postmaster -i -D
/var/lib/pg</div><div><br/>When you install the DB, the logs are enabled by default?</div><div> </div><div>Would you
plstell me still what setting need to be done?</div><div> </div><div>Thanks,<br />Vinayak V. Raikar<br />Extn : 143<br
/><br/></div></font></div></div></font> 

Re: DB problem

От
"Albe Laurenz"
Дата:
> We are using PostgreSQL 7.3 version, installed in linux
> system. Only DB is getting shut down 3-4 times a day. From my
> application end I get "Sorry too many clients" error.
> Refering the FAQ I maximized the DB session limit to 200.
>
> I think the logs are not enabled in my DB. So I set the
> following options in postgresql.con file
>
> log_timestamp= true
> log_directory=pg_log
> log_filename=%Y-%m-%d_%H%M%S.log
> log_disconnections=true
> log_hostname=true
> log_statement=true
>
>
> After restarting the system got the following error :
>  FATAL: postgresql.conf:131: syntax error, token="%"
>  FATAL: postgresql.conf:131: syntax error, token="%"
>  FATAL: postgresql.conf:131: syntax error, token="%"
>  FATAL: 'log_directory' is not a valid option name
>  FATAL: 'log_directory' is not a valid
>  FATAL: 'log_filename' is not a valid option name
>  FATAL: 'log_disconnections' is not a valid option name
>
> When you install the DB, the logs are enabled by default?
>
> Would you pls tell me still what setting need to be done?

You can see in the documentation:
http://www.postgresql.org/docs/7.3/static/runtime-config.html#LOGGING

The parameters you used are for a different version of PostgreSQL.

Yours,
Laurenz Albe

Re: DB problem

От
"Filip Rembiałkowski"
Дата:
2006/12/26, vinayakr@vmoksha.com <vinayakr@vmoksha.com>:

> I think the logs are not enabled in my DB. So I set the following options in
> postgresql.con file

you are using some options which came with later postgresql releases.

> log_timestamp= true
ok
> log_directory=pg_log
wrong (available from 8.0)
> log_filename=%Y-%m-%d_%H%M%S.log
wrong (available from 8.0)
> log_disconnections=true
wrong (available from 8.0)
> log_hostname=true
wrong (available from 7.4)
> log_statement=true
OK

you can review all runtime options for 7.3 here:
http://www.postgresql.org/docs/7.3/static/runtime-config.html


> When you install the DB, the logs are enabled by default?
> Would you pls tell me still what setting need to be done?

for 7.3, the default was to log to standard output.
so you will have to redirect it, either to syslog (by setting syslog =
1), or to a file using shell redirection, or with pg_ctl option.
see http://www.postgresql.org/docs/7.3/static/app-pg-ctl.html


F.