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)---
T
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
my English,
Thanks,
Bart Golda
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
ve 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
...
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
-
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
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
a, 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)---
