Re: [GENERAL] Because PostgreSQL is compiling in old versions of OS?

Oh!! Jose Maria TJ wrote > You're wrong, that are gcc versions, not OS versions. > > For example in my CentOS 6 Box > > cat /etc/redhat-release > CentOS release 6.9 (Final) > > gcc -v > [...trimmed...] > gcc versión 4.4.7 20120313 (Red Hat 4.4.7-18) (GCC) You're right!. Is the GGC version,

[GENERAL] Because PostgreSQL is compiling in old versions of OS?

Hi everyone! I want to develop a installer for many purposes, but i have a question, when I review the currently PostgreSQL versions, I see Ubuntu 5 or RHEL 4 , when currently we have Ubuntu 16 or RHEL 7. for example: /PostgreSQL 9.6.0 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.4.7

Re: [GENERAL] postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting

You're right I have forgotten to say, the OS is RHEL 7. Actually I'm reading about. Thanks! - Dame un poco de fe, eso me bastará. Rozvo Ware Solutions -- View this message in context:

Re: [GENERAL] postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting

> Do you control the app? Nop Just I know how it's developed. > The app has a pooling component and you still are having problems, have > you looked at what the pooler is actually doing? As far as I know, the wildfly's jdbc pool. No really I don't know what are doing. I suspect that problem

Re: [GENERAL] postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting

To expand information, the application are written in Grails on wildfly with pool connections. I didn't have time to check pg_locks with detail, I'll configure the connections logs to monitoring those. I can't close connections on the application side. How I close connections on the database

Re: [GENERAL] postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting

Yep, the real problem was all connections are used up. A ps command showed this: postgres 1172 23340 1 13:00 ?00:01:23 postgres: dbsomething dbsomething 8.8.8.1[34024] PARSE waiting postgres 1527 23340 3 13:07 ?00:02:47 postgres: dbsomething dbsomething 8.8.8.2[49193] PARSE

[GENERAL] postgres: dbname dbuser 9.9.9.9[2222] PARSE waiting

Hi folks. Today I had a problem with production's database PostgreSQL version 9.4.4.9. The server have max_connections set to 200, but today I reviewed pg_stat_activity and saw 199 active connections, obviously the server rejected any new connection and the production stopped. I saw another

[GENERAL] With the password stored a another database, how to securely connecting to server

Hi folks I've a questions about the secure conections. I'm designed a local app with a micro database with h2 (is the java app), this app connect to PostgreSQL with many users. I want store password encrypted with md5 in the microdb. But my question, with this encrypted password. How to securely

Re: [GENERAL] The same query is too slow in some time of execution

You're right, I'm sorry. At the moment, we review the schema for tables and indexes and decided redesigned. I detected a loop in the join, because we only have a integer sequencial like PK and no composite keys in the tables. I think that is the mainly problem. Thanks! - Dame un poco de

[GENERAL] The same query is too slow in some time of execution

! DRakoROd - Dame un poco de fe, eso me bastará. Rozvo Ware Solutions -- View this message in context: http://www.postgresql-archive.org/The-same-query-is-too-slow-in-some-time-of-execution-tp5951060.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. -- Sent via

[GENERAL] Re: could not load library "$libdir/sslutils": in pg_upgrade process

Adrian, Tom Finally I did upgrade version but I've removed database pem (Postgres Enterprise Manager) I guess that this database has some link in some function to sslutils, because pg_upgrade showed the above errors while upgraded this database. /pg_restore: creating FUNCTION

[GENERAL] Re: could not load library "$libdir/sslutils": in pg_upgrade process

Teorycally, I removed the sslutils from old cluster when review the $libdir appear this: /[postgres@server ~]$ /opt/PostgreSQL/9.3/bin/pg_config --pkglibdir /opt/PostgreSQL/9.3/lib/postgresql [postgres@server ~]$ /opt/PostgreSQL/9.3/bin/pg_config --libs -lpgport -lpgcommon -lxslt -lxml2 -lpam

[GENERAL] Re: could not load library "$libdir/sslutils": in pg_upgrade process

Yes I installed Postgres Enterprise Manager Agent time ago in this server to test agent, but now I don't use it. Amm if you refer the EDB install with binaries PostgreSQL one-click yes, but is not a EDB Advanced Server , is a normal Cluster installed by EDB binaries. - Dame un poco de fe,

[GENERAL] could not load library "$libdir/sslutils": in pg_upgrade process

stgresql/sslutils.so" Command was: CREATE FUNCTION "sslutils_version"() RETURNS "text" LANGUAGE "c" IMMUTABLE AS '$libdir/sslutils', 'sslutils_version'... / Then, I try uninstall the sslutils in the old cluster and recreate new cluster clean of 9.6.1,

Re: [GENERAL] FATAL: semctl(999999, 6, SETVAL, 0) failed: Invalid argument

Hi Tom! Thanks for your quick response, in fact, it is not a problem with NAS storage. It is the systemd configuration. I had detected that the semaphores were removed every 20-30 minutes. After that configuration (the links that you share), I monitored during 1 hour and everything is going

[GENERAL] FATAL: semctl(999999, 6, SETVAL, 0) failed: Invalid argument

Hi everybody I have a problem with to Postgres 9.5 with the semaphores, mainly in the Standby node, but in the mater node has been happening too. The implementation are in RedHat 7.2 with the NAS Storage, the data directory of PostgreSQL is in the NAS storage. I was read that PostgreSQL doesn't

Re: [GENERAL] I can't see wal receiver process in one node

production node failed and the node B had that resync up the replication with another production node. My question. This parameter if not disabled affect the replication? Best Regards! DrakoRod - Dame un poco de fe, eso me bastará. Rozvo Ware Solutions -- View this message in context

[GENERAL] I can't see wal receiver process in one node

ade replication? Best regards DrakoRod - Dame un poco de fe, eso me bastará. Rozvo Ware Solutions -- View this message in context: http://postgresql.nabble.com/I-can-t-see-wal-receiver-process-in-one-node-tp5896950.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. -- S

[GENERAL] FATAL: unable to read data from DB node 0

. Any suggestions? Best regards! DrakoRod - Dame un poco de fe, eso me bastará. Rozvo Ware Solutions -- View this message in context: http://postgresql.nabble.com/FATAL-unable-to-read-data-from-DB-node-0-tp5875389.html Sent from the PostgreSQL - general mailing list archive at Nabble.com

Re: [GENERAL] password in recovery.conf

Hi! Have you tried escape the Single or Double quote? Maybe this information can help you: http://stackoverflow.com/questions/12316953/insert-varchar-with-single-quotes-in-postgresql http://www.postgresql.org/docs/9.1/static/sql-syntax-lexical.html Best Regards! - Dame un poco de fe,

Re: [GENERAL] Server continuously enters to recovery mode.

Hi everybody Thank you for your help! I upgrade the version of 9.0.15 to 9.0.17. But after that constantly show this error, in all sessions: *WARNING: terminating connection because of crash of another server process DETAIL: The postmaster has commanded this server process to roll

[GENERAL] Server continuously enters to recovery mode.

Hi everybody! I have a problem (really huge problem), I have one server of production, but yesterday in the night I saw this error: *ERROR: could not access status of transaction 2410303155 DETAIL: Could not open file pg_clog/08FA: No such file or directory* Solution: * dd