Re: [GENERAL] A pg_hba.conf problem - again...
Problem solved, keys issue. I'm just not good in configuring a linux server. Solution is here: http://developer.postgresql.org/docs/postgres/ssl-tcp.html I did it and then turned ssl on in the postgresql.conf file. Works. ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [GENERAL] SSL or other libraries for Windows-to-Linux PostgreSQL connection?
For future generations: It is solved. Do whatever http://developer.postgresql.org/docs/postgres/ssl-tcp.html says, than turn on ssl in postgresql.conf and restart PostgreSQL. Regards, Bart Golda ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[GENERAL] SSL or other libraries for Windows-to-Linux PostgreSQL connection?
Hi, I posted almost similar question before, but my idea about the problem has changed so it makes a new problem. So I create a new thread :) Windows machines do not want to connect to a Linux PostgreSQL server 8.1, works only trust authentication for them. I saw an old 7.2 server, it had the same problem. Windows uses allow autentication. Pg_hba seems to be all right (connection can be estabilished, but only with 'trust'). I was informed that Linux and/or Windows may miss some crypto libraries. I will install all crypto-* rpms I can find :), but 1) Are there any libraries that should be installed on Windows machine (except for pgsqlODBC) to allow non-trust connections (e.g. MD5)? 2) Is it possible that rpm installations (for Fedora III) did not inform me, that some libraries, essential for crypted connections are missing? If yes, what libraries could that be? Sorry for my English, Thanks, Bart Golda ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[GENERAL] A pg_hba.conf problem - again...
So there is Fedora Core 3 with PostgreSQL 8.1.3 installed from rpms. The server listens on all interfaces. For testing, I used this pg_hba.conf (default with added line) and it worked: local all all trust host all all 127.0.0.1/32 trust host all all ::1/128 trust host all all 10.144.3.0/24 trust Very happy, I changed trust in the last line to MD5. The application (pgAdmin) stopped connecting (yes, sql user and its password was correct). No error, just "unable to connect" or something like this - I have localised version - in the status line. Is there something wrong with above file or maybe there are some missing libraries, of which I (and rpms) am not aware of? :( Thanks for any suggestions, Bart Golda ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[GENERAL] PgsqlODBC connection parameters in the registry
Is there any way to crypt ODBC settings (user, password)? It seems to be stored in HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI in plain text. I can use bogus data there and "cover" it with proper login and password on application side, but... er... MSSQL does not store password in this way... It is probably possible to prevent user from reading the values in the registry, but it is a sort of a whole-system-not-application setting. It seems that this way of storing information can be unsafe in certain circumstances and so on... Thanks in advance, Bart Golda ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[GENERAL] Quick psqlODBC driver setting
I would like to have an installation program, which creates psqlODBC connection, so there will be no need of typing and clicking on two hundred workstations... There is the driver's msi file which can be installed very nicely, but what is the best way of creating the connection itself without much pain? My current idea is like this: 1. Exporting the entry "CONNECTION_NAME" REG_SZ "PostgreSQL ANSI" from HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources 2. Exporting HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\CONNECTION_NAME 3. Running the reg file(s) on the target machine Well, it works - more or less - but is this a *right way*? How do *you* do it? Regards, Bart Golda ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [GENERAL] Connecting process to PostgreSQL works stunningly slow
Thanks for hints! In case of anyone having similar problem - it can be easily solved. Windows 2003 Server deserves painful death! It just stopped answering pings and most of the network traffic was terribly slow (MS SQL Server worked, though... strange). Restarting the Windows server helped - everything works now. We could not do it before (very important users, MS SQL Server, other wonderful things). I suppose the problem was not in any way connected with PostgreSQL. Someone told me that many W2003S configurations (especially with some server services running) require weekly restart to work well. Just in case, PostgreSQL server will be probably moved in some time to Solaris or some *nix... Thanks, Bart Golda ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[GENERAL] Connecting process to PostgreSQL works stunningly slow
Hi, We have a problem with PostgreSQL 8.1 on a production server (Windows 2003 Server, Xeon 3GHz, 1GB)); application placed on it run for a month without problems. It was great. But yesterday... Any connection to the server, from application or pgAdmin (both previously working fine), is slow. I mean, I have to wait *minutes* for even login to succeed. Even when connecting from the same machine, with pgAdmin, with no users connected to it. Restarting the service is slow, opening the database is slow, backup is slow. Sometimes minutes, I mean. Like there was something wrong with listening for connections - sometimes I got an information that server on [my_ip_here:my_port_here] is not listening. The machine runs other services, but there is no heavy load on it and users do not have any problems with e.g. (don't shoot) MS SQL Server. Since I use IPs only, DNS issues should not be involved. There were no changes to current configuration, autovacuum is on and it seems to work, according to the log (runs every 60s). There are two tiny tables (no more than a hundred rows each, barely a database), there are only updates on them (no more than a few hundreds a day), I know it's weird but that's how it should work. I googled and searched on Groups. I'm rather new with PostgreSQL and dealing with the crashed production server is not nice :) Tommorrow I will try connection without md5 and look if the drive is OK (defragmentation?), but maybe someone has any idea, what else could I check? It is very depressing, since the database is so tiny... If nothing else helps, I will of course pg_dump, reinstall PostgreSQL server and wait for a month or so *gulp*. Thanks in advance, Bart Golda ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
