[ADMIN] reg:conninfo

hi,       I am using postgres8.0.3 on windows.When i am compiling a small sample i am facing problem in connection information.   I have given entry in my pg_hba.conf file: host    all all 10.0.3.67/32  md5    And in my application when

Re: [ADMIN] reg:conninfo

Try looking at the manual for the postmaster process ... A simple way of achieving what you want is adding the -i option to the postmaster command line which allows TCP/IP connections. Otherwise only localhost can connect. There are possibly other ways of configuring this same option, but we

Re: [ADMIN] reg:conninfo

Thanks Robin. What u said is right! But my problem is i am not trying connecting from any remote client. In my ConnectionInfo if i mention the host as, host=localhost.The connection is successful. But the same if i give my localsystem IP where my server is running.. host = 10.0.2.56(my localhost

Re: [ADMIN] reg:conninfo

Sandhya, You have mentioned 3 different IP addresses for your server in this topic so far. Your pg_hba.conf entry says "10.0.3.67/32" - which means only that IP can connect - the IP address/range in pg_hba.conf should be your client IP (if this is on the same server as PGSQL, the best way is to u

Re: [ADMIN] reg:conninfo

You should be able to connect if you tell your application to connect to 127.0.0.1, and put Hostall all 127.0.0.1/32md5 In your pg_hba.conf file - this is a system default loopback IP for clients on the same machine. Why is it causing you such a problem using localhost as opposed

Re: [ADMIN] reg:conninfo

Host all all 127.0.0.1/32 md5 This entry is there in configuration file already.So no probs..I can connect. But..Just i want to know why it is connecting if i mention just localhost and why it giving error if i mention the IP of it(the same m/c's) instead of local host. Have u seen the image i sen

FW: [ADMIN] reg:conninfo

If you put localhost in your application, your system (Windows or Linux) will do a DNS lookup and return the 127.0.0.1 IP - if you put the IP directly it saves this call. Check your postgresql.conf file, and look for the listen_interfaces directive - check it's set to listen_interfaces=*, and not

Re: [ADMIN] reg:conninfo

Sandhya, If you use localhost you will be creating a UNIX domain socket. If you use the IP address you will create a TCP/IP socket. Did you try running with -i yet? It doesn't mean accept remote connections, it means accept TCP/IP connection. Without it, you cannot connect to an IP addre

Re: [ADMIN] reg:conninfo

Robin, I believe this is on a Windows machine (judging by the screenshot I was sent of the error message.) I think it's that PGSQL is set to only listen on the localhost IP. Andy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robin Iddon Sent: Monday,

Re: [ADMIN] reg:conninfo

Check you've not got a firewall blocking port 5432. If running Windows firewall on XP/2003, you'll need to set an exception for port 5432. As you're on a windows system run "ipconfig" from a command prompt, and note down the IP addresses on your network interfaces. Then set listen_interfaces t

Re: [ADMIN] reg:conninfo

Yes Andy..Thats what i did. i checked by giving '*' in listen_address also i gave IP of my system.Both things got failed. Whether reload is enough... or we need to restart it? - Original Message - From: "Andy Shellam" <[EMAIL PROTECTED]> To: "'sandhya'" <[EMAIL PROTECTED]> Cc: Sent: Mond

Re: [ADMIN] reg:conninfo

Hi Andy, Now it is working fine.After mentioning listen_address = '*' ..I have restarted the postgres server. Then it is working fine. Thanks for your help. -Sandhya - Original Message - From: "Andy Shellam" <[EMAIL PROTECTED]> To: "'sandhya'" <[EMAIL PROTECTED]> Cc: Sent: Monday,

Re: [ADMIN] reg:conninfo

I'm sorry, please don't confuse a UNIX domain socket with "localhost" which are _not_ the same at all. A UNIX domain socket is nothing more than a file *usually* located in a temporary directory, used for inter-process communication. "localhost" - 127.0.0.1, also used on any TCP/IP configured

Re: [ADMIN] reg:conninfo

localhost 127.0.0.1--->What is the importance of it? Is there any document to know about this? - Original Message - From: "Louis Gonzales" <[EMAIL PROTECTED]> To: "Robin Iddon" <[EMAIL PROTECTED]> Cc: "Postgres" Sent: Monday, March 20, 2006 5:59 PM Subject: Re: [ADMIN] reg:conninfo

Re: [ADMIN] reg:conninfo

http://en.wikipedia.org/wiki/Loopback sandhya wrote: localhost 127.0.0.1--->What is the importance of it? Is there any document to know about this? - Original Message - From: "Louis Gonzales" <[EMAIL PROTECTED]> To: "Robin Iddon" <[EMAIL PROTECTED]> Cc: "Postgres" Sent: Monday, M

[ADMIN] PostgreSQL zope equivalent of PHPpgAdmin

Hi , Anyone aware of a PHPpgAdmin equivalent in zope. -- With Best Regards, Vishal Kashyap. http://www.vishal.net.in ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your

[ADMIN] could not accept SSL connection: peer did not return a certificate

Hello, I am attempting to upgrade a 7.4.x server to a 8.0.x server.   I have read the release notes and read the administration documentation for changes to SSL requirements and cannot find anything that suggests SSL connections have changed.   Yet when I try to connect with old client applic

Re: [ADMIN] could not accept SSL connection: peer did not return a

On Mon, 20 Mar 2006, Donald Fraser wrote: Yet when I try to connect with old client applications using SSL I get the following error reported in the server log: "could not accept SSL connection: peer did not return a certificate" Donald, Are you attempting to use SSL certificates for client

Re: [ADMIN] use of in psql

On Mar 18, 2006, at 6:15 PM, Bruce Momjian wrote: Luis P. Mendes wrote: When I connect to a database via psql and do a select * from table; I get the first page of results, considering \pset pager is on. In Debian, I can press the key to go directly to the last results or I can use or to

[ADMIN] Starting in a Windows administrative account

Title: Starting in a Windows administrative account In the thread: Fix for running from admin account on win32 http://archives.postgresql.org/pgsql-patches/2006-01/msg00172.php An optimistic reading is that postgresql will be able to drop dangerous permissions as it starts up instead of re

Re: [ADMIN] could not accept SSL connection: peer did not return a

> > Yet when I try to connect with old client applications using SSL I get > > the following error reported in the server log: > > "could not accept SSL connection: peer did not return a certificate" > Are you attempting to use SSL certificates for client authentication? It > sounds like you have

Re: [ADMIN] Starting in a Windows administrative account

> In the thread: > > Fix for running from admin account on win32 > > http://archives.postgresql.org/pgsql-patches/2006-01/msg00172. > php > > > An optimistic reading is that postgresql will be able to drop > dangerous permiss

Re: [ADMIN] Starting in a Windows administrative account

To add and compile the source I can follow the instructions here: http://www.postgresql.org/docs/faqs.FAQ_MINGW.html but I am not sure where to put the patches to have them included or whether I should use the ./configure and its arguments to include them. Any advice would be appreciated. I have

Re: [ADMIN] Starting in a Windows administrative account

> To add and compile the source I can follow the instructions here: > http://www.postgresql.org/docs/faqs.FAQ_MINGW.html > > but I am not sure where to put the patches to have them > included or whether I should use the ./configure and its > arguments to include them. Any advice would be appreci

[ADMIN] Character encoding problems and dump import

Hello, I have a dump (non-binary, if it matters) of a DB that has some characters in it that my DB doesn't want to take. I'm using PG 8.0.3 and it was created with Unicode support: => \encoding UNICODE Characters that cause problems during the import are things like: é and other characters from

[ADMIN] hiding the postgres password - v8.1.0

Hi, Is there a way to hide or encrypt the postgres password when the postgres user is required to be the user in a shell script? This way we could have a function called in a program, and the users could do something with out actually seeing the postgres user password. We have tried puttin

Re: [ADMIN] hiding the postgres password - v8.1.0

Mr. Dan wrote: > Is there a way to hide or encrypt the postgres password when the postgres > user is required to be the user in a shell script? This way we could have > a function called in a program, and the users could do something with out > actually seeing the postgres user password. See

Re: [ADMIN] hiding the postgres password - v8.1.0

On Mon, Mar 20, 2006 at 17:23:43 -0400, Alvaro Herrera <[EMAIL PROTECTED]> wrote: > Mr. Dan wrote: > > > Is there a way to hide or encrypt the postgres password when the postgres > > user is required to be the user in a shell script? This way we could have > > a function called in a program,

Re: [ADMIN] Character encoding problems and dump import

Am Montag, 20. März 2006 21.21 schrieb [EMAIL PROTECTED]: > Hello, > > I have a dump (non-binary, if it matters) of a DB that has some characters > in it that my DB doesn't want to take. I'm using PG 8.0.3 and it was > created with Unicode support: > > => \encoding > UNICODE This is the client enc

[ADMIN] encoding question

Hi, My main server is on Solaris (LANG=C), postgresql 8.1.0, with encoding SQL_ASCII. I'm trying to set up a backup server on linux (LANG=en_US.UTF-8), with encoding UTF8. I thought UTF8 was safe if all I have is ascii, since there was a relevant discussion in this list a short while ago,

Re: [ADMIN] encoding question

Am Montag, 20. März 2006 23.56 schrieb Ben K.: > Hi, > > My main server is on Solaris (LANG=C), postgresql 8.1.0, with encoding > SQL_ASCII. SQL_ASCII is not an encoding. It marks that there is no encoding and therefore no check of the stored byte codes. This means that the client is fully respo

Re: [ADMIN] encoding question

"Ben K." <[EMAIL PROTECTED]> writes: > I thought UTF8 was safe if all I have is ascii, It is, but evidently what you have is not all ASCII. > ERROR: invalid UTF-8 byte sequence detected near byte 0x85 Looks to me like it might have been meant as LATIN1 or one of the other single-byte ASCII-exte

Re: [ADMIN] Character encoding problems and dump import

On Mar 20, 2006, at 3:21 PM, <[EMAIL PROTECTED]> [EMAIL PROTECTED]> wrote: The data may not be the cleanest, and I have limited control over that. But I am wondering if there is any way I can import this data, even if that means converting some of the characters into something else. incon