"Scott Marlowe" writes:
> On Mon, Dec 29, 2008 at 2:23 PM, Carol Walter wrote:
>> ... I can't connect to the database instance
>> from a remote host. I get a message as follows:
>> walt...@cat:~$ psql -h db -U walterc -d walterc -p 5433
>> psql: could not connect to server: Connection refused
>>
On Mon, Dec 29, 2008 at 04:23:30PM -0500, Carol Walter wrote:
> "with openssl" when I initially configured the server. Are there other
> things that need to be done to get openssl started on the database server?
> How can I diagnose this problem?
>
The files server.key, server.crt, root.crt, a
On Mon, Dec 29, 2008 at 2:23 PM, Carol Walter wrote:
> Hello,
>
> I've just created a new instance of postgres. It's running an a Sun server
> running Solaris 10. I configured it with ssl using port 5433. The server
> starts and runs. I can connect to it from the local host and list the
> data
>>> Carol Walter wrote:
> The server starts and runs. I can connect to it from the local host
> and list the databases, connect to them etc. I can't connect to the
> database instance from a remote host.
Have you set listen_addresses in postgresql.conf?
You likely want:
listen_address
Hello,
I've just created a new instance of postgres. It's running an a Sun
server running Solaris 10. I configured it with ssl using port 5433.
The server starts and runs. I can connect to it from the local host
and list the databases, connect to them etc. I can't connect to the
data
Laszlo Nagy writes:
> maybe is it possible to change the source code, and disable the "is
> postmaster alive" check for testing?
Rather than disabling it, it'd probably be more convenient to make
any getppid value except 1 (the init process) be treated as "it's
alive". Otherwise you'll have tro
Tom Lane wrote:
Alvaro Herrera writes:
Tom Lane wrote:
I wonder whether your tracing tool is affecting the result of
getppid(). Most people would consider that a bug in the tracing tool.
I wrote to an official the FreeBSD list about this getppid() problem but
got no answe
