Dear all,
After setting log_statement='all' at postgres.conf,
then i'm rebooting OS [freeBSD or CentOS],
i can't find where log file created from log_statement='all' located...
FYI, location of postgres.conf at /var/lib/pgsql/data/postgres.conf
many thanks..
Regards,
Joko [SYSTEM]
PT. Indra Jaya
Hi List,
I am using pgsql 7.4.2 on solaris-9. When I start the postgres with "-i"
option as below, the processes of the postgres are increasing
drastically.
pg_ctl start -D /db1/postgresql/data -o "-i"
If I exclude "-I" option, my application couldn't connect the DB server
at all.
Here are my q
Στις Thursday 17 July 2008 11:43:28 ο/η System/IJS - Joko έγραψε:
> Dear all,
>
> After setting log_statement='all' at postgres.conf,
> then i'm rebooting OS [freeBSD or CentOS],
> i can't find where log file created from log_statement='all' located...
> FYI, location of postgres.conf at /var/lib/
Inside the database, you can query the pg_settings table.
select * from pg_catalog.pg_settings where name = 'log_directory';
To see other stuff you can get from that table, try:
select name from pg_catalog.pg_settings;
--- On Thu, 7/17/08, Achilleas Mantzios <[EMAIL PROTECTED]> wrote:
From:
On Thu, Jul 17, 2008 at 02:46:58PM +0530, Suresh Gupta VG wrote:
> Hi List,
>
> I am using pgsql 7.4.2 on solaris-9.
Go and upgrade that right away. It has several very nasty bugs in
it. 7.4.21 is the latest.
> pg_ctl start -D /db1/postgresql/data -o "-i"
>
> If I exclude "-I" option, my app
Hi
Below is the locks that are generated by my program. Can someone thrown some
light as to why i see multiple locks on the same table?.
I first insert data in the table 'imputed_prediction' and the select data
from it..since i see locks on indexes.iam
assuming i
