[ADMIN] Logs say update done but not actually done or committed into database ???

2009-04-22 Thread Atul Chojar
We are facing a strange problem in our 8.2.7 database. There is a bash shell script that does:- sql=select distinct to_char(date_of_issue, 'MM') from yan.int_prod_s_master order by 1; MM=`/usr/local/pgsql/bin/psql -U postgres -h payday -d sandbox -t -c $sql` for x in $MM do

Re: [ADMIN] Logs say update done but not actually done or committed into database ???

2009-04-22 Thread Scott Marlowe
On Wed, Apr 22, 2009 at 2:28 PM, Atul Chojar acho...@airfacts.com wrote: We are facing a strange problem in our 8.2.7 database. There is a bash shell script that does:- sql=select distinct to_char(date_of_issue, 'MM') from yan.int_prod_s_master order by 1;

Re: [ADMIN] Logs say update done but not actually done or committed into database ???

2009-04-22 Thread Tom Lane
Scott Marlowe scott.marl...@gmail.com writes: On Wed, Apr 22, 2009 at 2:28 PM, Atul Chojar acho...@airfacts.com wrote: Any ideas why above update is not working? Any possibility you're doing the updates to an inherited table, or a table in a different schema or a different database than you

[ADMIN] Logs perms and ownership

2008-08-25 Thread steve
Hi all, Is there a way to make the postgres logs readable by other users or a group apart from postgres:postgres? I am on postgres 8.1 I cannot see any feature to allow setting perms or ownership Thanks Steve -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes

Re: [ADMIN] Logs perms and ownership

2008-08-25 Thread Joshua Drake
On Tue, 26 Aug 2008 14:11:13 +1200 Steve Holdoway [EMAIL PROTECTED] wrote: On Tue, 26 Aug 2008 10:42:19 +1000 [EMAIL PROTECTED] wrote: Hi all, Is there a way to make the postgres logs readable by other users or a group apart from postgres:postgres? I am on postgres 8.1 I

Re: [ADMIN] Logs perms and ownership

2008-08-25 Thread steve
Yeah, thought about that but as you said the perms on the logs are 700. on both stderr and syslogging. On Mon, 25 Aug 2008 19:22:45 -0700, Joshua Drake [EMAIL PROTECTED] wrote: On Tue, 26 Aug 2008 14:11:13 +1200 Steve Holdoway [EMAIL PROTECTED] wrote: On Tue, 26 Aug 2008 10:42:19 +1000

Re: [ADMIN] Logs perms and ownership

2008-08-25 Thread steve
Correction, perms are 600. On Mon, 25 Aug 2008 19:22:45 -0700, Joshua Drake [EMAIL PROTECTED] wrote: On Tue, 26 Aug 2008 14:11:13 +1200 Steve Holdoway [EMAIL PROTECTED] wrote: On Tue, 26 Aug 2008 10:42:19 +1000 [EMAIL PROTECTED] wrote: Hi all, Is there a way to make the postgres

[ADMIN] Logs

2004-12-13 Thread Marek Dabrowski
Hello Dear friends, I have one problem. My postgres 7.4.6 is working on HP DL360G4 with 2 disks working in mirror. Normaly average quantity postmaster proceses is 5-30 but when I switch on loging: syslog=2 log_connections = true log_hostname = true fsync = false quantity of postmasters grow up

Re: [ADMIN] logs file

2001-05-11 Thread Lamar Owen
On Tuesday 08 May 2001 12:23, [EMAIL PROTECTED] wrote: I have installed postgresql 7.x on red hat 7.0 and I have created a database and users. I would like now to see in a log file history of operations on the database, different connexions of users to the database... Can you give me the

[ADMIN] logs file

2001-05-08 Thread [EMAIL PROTECTED]
I have installed postgresql 7.x on red hat 7.0 and I have created a database and users. I would like now to see in a log file history of operations on the database, different connexions of users to the database... Can you give me the steps please ? I have read that Syslog can be needed but I

[ADMIN] logs

2001-04-26 Thread [EMAIL PROTECTED]
my options in pg_options are: verbose=2 query hostlookup showportnumber syslog=2 what is the line I have to write in the /etc/syslog.conf in order to see events of databases ? __ Voila vous propose une boite aux lettres gratuite sur Voila

Re: [ADMIN] logs

2001-04-25 Thread Lamar Owen
[EMAIL PROTECTED] wrote: I want to view events about my databases on a log file For version 7.0.x in the RPM distribution: 1.) Enable syslog in pg_options (see documentation on the levels necessary) 2.) Add a line to /etc/syslog.conf for local1 to go to the file you want. 3.)