Re: [GENERAL] FATAL: database "a/system_data" does not exist

2013-05-17 Thread sumita
I found the configuration XML file which was creating the problem.By changing the database name , it solved the problem.Since there was also check-valid-connection-sql, it was happening at a particular frequency. Thanks all! -- View this message in context: http://postgresql.1045698.n5.nabble.

Re: [GENERAL] FATAL: database "a/system_data" does not exist

2013-05-16 Thread Adrian Klaver
On 05/16/2013 05:31 AM, sumita wrote: I am running greps to find out what could be triggering it. in the scripts and programs. My only other concern is the same version of my product works without this log statements in the Postgres 9.1.3 version.Once upgraded to 9.2.4 , these log statements are

Re: [GENERAL] FATAL: database "a/system_data" does not exist

2013-05-16 Thread sumita
I am running greps to find out what could be triggering it. in the scripts and programs. My only other concern is the same version of my product works without this log statements in the Postgres 9.1.3 version.Once upgraded to 9.2.4 , these log statements are appearing. -- View this message in co

Re: [GENERAL] FATAL: database "a/system_data" does not exist

2013-05-15 Thread Tom Lane
Adrian Klaver writes: > On 05/15/2013 05:45 AM, sumita wrote: >> Also,so far I have unable to find out which process is invoking this query. >> I do see the process id in the logs but I am unable to see this process id >> in pg_stat_activity table.. > Actually a\system_data is not part of a quer

Re: [GENERAL] FATAL: database "a/system_data" does not exist

2013-05-15 Thread Adrian Klaver
On 05/15/2013 05:45 AM, sumita wrote: The database name is "a" and the "system_data" appears within the Schemas. When I list the database from psql, I get following report Name| Owner | Encoding | Collate |Ctype| Access privileg es ---+--+--+---

Re: [GENERAL] FATAL: database "a/system_data" does not exist

2013-05-15 Thread sumita
The database name is "a" and the "system_data" appears within the Schemas. When I list the database from psql, I get following report Name| Owner | Encoding | Collate |Ctype| Access privileg es ---+--+--+-+-+-- -

Re: [GENERAL] FATAL: database "a/system_data" does not exist

2013-05-14 Thread Adrian Klaver
On 05/14/2013 03:30 AM, sumita wrote: I put the log_statement to 'all' and log_connections too. I get below May 14 09:18:45 LOG: execute : SELECT gid FROM pg_prepared_xacts May 14 09:18:45 LOG: connection received: host=127.0.0.1 port=55618 May 14 09:18:45 LOG: connection authorized: user=po

Re: [GENERAL] FATAL: database "a/system_data" does not exist

2013-05-14 Thread sumita
Has anything changed in terms of search_path in postgres 9.2.4 I have upgraded postgres from 9.1.3 where I donot see these errors in the log file -- View this message in context: http://postgresql.1045698.n5.nabble.com/FATAL-database-a-system-data-does-not-exist-tp5754839p5755399.html Sent from

Re: [GENERAL] FATAL: database "a/system_data" does not exist

2013-05-14 Thread sumita
Further analysis on my product code does not show this query being fired from the product code at interval. Not sure which application is invoking this at every 130 seconds -- View this message in context: http://postgresql.1045698.n5.nabble.com/FATAL-database-a-system-data-does-not-exist-tp575

Re: [GENERAL] FATAL: database "a/system_data" does not exist

2013-05-14 Thread sumita
I put the log_statement to 'all' and log_connections too. I get below May 14 09:18:45 LOG: execute : SELECT gid FROM pg_prepared_xacts May 14 09:18:45 LOG: connection received: host=127.0.0.1 port=55618 May 14 09:18:45 LOG: connection authorized: user=postgres database=a/system_data May 14 09

Re: [GENERAL] FATAL: database "a/system_data" does not exist

2013-05-10 Thread Tom Lane
Adrian Klaver writes: > On 05/10/2013 12:13 AM, sumita wrote: >> This error is getting logged at an interval of 2 minutes and 10 seconds >> 2013-05-10 00:22:50 GMT:[4180]FATAL: database "a/system_data" does not >> exist > A suggestion, turn up your log_statement to 'all' to see if you can > cat

Re: [GENERAL] FATAL: database "a/system_data" does not exist

2013-05-10 Thread Adrian Klaver
On 05/10/2013 12:13 AM, sumita wrote: This error is getting logged at an interval of 2 minutes and 10 seconds 2013-05-10 00:22:50 GMT:[4180]FATAL: database "a/system_data" does not exist 2013-05-10 00:25:00 GMT:[4657]FATAL: database "a/system_data" does not exist 2013-05-10 00:27:10 GMT:[

Re: [GENERAL] FATAL: database "a/system_data" does not exist

2013-05-10 Thread Chris Angelico
On Fri, May 10, 2013 at 5:13 PM, sumita wrote: > This error is getting logged at an interval of 2 minutes and 10 seconds > 2013-05-10 00:22:50 GMT:[4180]FATAL: database "a/system_data" does not > exist > 2013-05-10 00:25:00 GMT:[4657]FATAL: database "a/system_data" does not > exist > 2013-05-

Re: [GENERAL] FATAL: database "a/system_data" does not exist

2013-05-10 Thread sumita
This error is getting logged at an interval of 2 minutes and 10 seconds 2013-05-10 00:22:50 GMT:[4180]FATAL: database "a/system_data" does not exist 2013-05-10 00:25:00 GMT:[4657]FATAL: database "a/system_data" does not exist 2013-05-10 00:27:10 GMT:[5394]FATAL: database "a/system_data" does

Re: [GENERAL] FATAL: database "a/system_data" does not exist

2013-05-09 Thread Adrian Klaver
On 05/09/2013 04:28 AM, sumita wrote: Hi All, I am observing some weird errors in the postgres logs after upgrading to Postgres 9.2.4. FATAL: database "a/system_data" does not exist What else happens right before the above message? We do have a user named "system_data" and a schema with the

[GENERAL] FATAL: database "a/system_data" does not exist

2013-05-09 Thread sumita
Hi All, I am observing some weird errors in the postgres logs after upgrading to Postgres 9.2.4. FATAL: database "a/system_data" does not exist We do have a user named "system_data" and a schema with the same name. Even with these error messages, we are actually able to access tables, sequences,