Does Postgres provides any native configuration support to fix residual space
in memory block.
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/residual-space-in-memory-block-tp5811424.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Se
Does postgresql support the use of security labels or sensitivity markings?
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/security-labels-or-sensitivity-markings-tp5811425.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pg
ss tables,
sequences, indexes, etc from that schema with out explicitly prefixing the
schema name to those relations.
Could anyone suggest what could be wrong with my setup and how to get past
it?
Thanks and Regards,
Sumita
--
View this message in context:
http://postgresql.1045698.n5.nabbl
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
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
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
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
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
---+--+--+-+-+--
-
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
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.
sent PGLOG and ARCHIVEDIR
but the recovery is not successful unless we send the FULL DATA Directory.
Please help us in resolving this problem whereby we do not have to send
the full DATA Directory.
The version of Postgresql is 8.0.3 on SuSe Linux 9.
Thanks and Regards
Sumita Chatterjee
11 matches
Mail list logo