Could Not Get Socket Error Status Invalid Argument
pgsql-announce pgsql-bugs pgsql-docs pgsql-general pgsql-interfaces pgsql-jobs pgsql-novice pgsql-performance pgsql-php pgsql-sql pgsql-students Developer lists Regional lists Associations User groups Project lists Inactive lists IRC Local User Groups Featured Users International Sites Propaganda Resources Weekly News Error - could not get socket error status: Invalid argument From: "Jayaraman, Rajaram (STSD)"
pgsql-announce pgsql-bugs pgsql-docs pgsql-general pgsql-interfaces pgsql-jobs pgsql-novice pgsql-performance pgsql-php pgsql-sql pgsql-students Developer lists Regional lists Associations User groups Project lists Inactive lists IRC Local User Groups Featured Users International Sites Propaganda Resources Weekly News Re: Error - could not get socket error status: Invalid argument From: simon
version and have compiled 64bit libpq library.While conneting I am getting error" could not get socket error status: Invalid argument"can someone help here? Why I am getting this error http://grokbase.com/t/postgresql/pgsql-general/12bq1rzgqn/invalid-argument while connecting to database.Regards reply Tweet Search Discussions Search All Groups PostgreSQL pgsql-general 1 response Oldest Nested Tom Lane Check into 32-vs-64-bit compilation options, and particularly whether PG's configure script chose the http://osdir.com/ml/postgresql-pgsql-general/2014-12/msg00434.html right type for the last argument to getsockopt(). I suspect it can be either 32 or 64 bits depending on compile options on HPUX, so it'd be an easy thing to could not mess up. regards, tom lane Tom Lane at Nov 23, 2012 at 11:39 pm ⇧ zhangshzh writes:I am working on hpux itanium platform;I am using postgres 9.1.3 version and have compiled 64bit libpq library.While conneting I am getting error" could not get socket error status: Invalid argument"Check into 32-vs-64-bit compilation options, and particularly whetherPG's configure script chose the right type for the could not get last argument togetsockopt(). I suspect it can be either 32 or 64 bits depending oncompile options on HPUX, so it'd be an easy thing to mess up.regards, tom lane reply | permalink Related Discussions FATAL : could not read directory base": Invalid argument Query postgres crashes - could not reattach to shared memory Error - could not get socket error status: Invalid argument "setsockopt(TCP_KEEPCNT) failed: Invalid argument" on Debian Lenny Could not read directory "pg_xlog": Invalid argument (on SSD Raid) Postgres 8.2 database recovery Could not create relation Invalid Argument could not write block could not open file "pg_subtrans/0014": Invalid argument Cause of ERROR: could not open relation 1663/856689/856777: Invalid argument? Discussion Navigation viewthread | post Discussion Overview grouppgsql-general @ Notice: Undefined variable: pl_domain_short in /home/whirl/sites/grokbase/root/www/public_html__www/cc/flow/tpc.main.php on line 1605 categoriespostgresql postedNov 23, '12 at 3:07a activeNov 23, '12 at 11:39p posts2 users2 websitepostgresql.org irc#postgresql Preferences responses expanded Hotkey:s font variable Hotkey:f user style avatars Hotkey:a 2 users in discussion Tom Lane (1) Zhangshzh (1) Content Home Groups & Organizations People Users Badges Support Welcome FAQ Contact Us Translate site design / logo © 2016 Grokbase
Vijay -- View this message in context: http://postgresql.nabble.com/Error-could-not-get-socket-error-status-Invalid-argument-tp1884036p5830654.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general Thread at a glance: Previous Message by Date: Re: [GENERAL] Blocking access by remote users for a specific time period Wouldn't it be a lot easier to set the database logins for those user accounts to zero allowed connections, then terminate their existing sessions, rather than mess with pg_hba.conf? You could schedule a cron job to run a query to make the change to the user, then later the same to undo the change. Scot Kreienkamp -----Original Message----- From: pgsql-general-owner@xxxxxxxxxxxxxx [mailto:pgsql-general-owner@xxxxxxxxxxxxxx] On Behalf Of Steve Atkins Sent: Sunday, December 14, 2014 1:02 PM To: pgsql-general@xxxxxxxxxxxxxx Subject: Re: [GENERAL] Blocking access by remote users for a specific time period On Dec 13, 2014, at 10:38 PM, Michael Nolan