From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
Cc: | 黄永卫 <yongwei(dot)huang(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Re: 答复: [GENERAL] About could not connect to server: Connection timed out |
Date: | 2009-10-20 14:56:01 |
Message-ID: | 27265.1256050561@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> writes:
> Anyway, let me make sure I understand what you are saying. After you
> reboot the server, just after the PostgreSQL service has started up,
> there are several minutes where some (but not all) client connections
> tend to time out. After that initial problem period, things start to
> work properly again and the time-outs stop happening. You only have
> problems shortly after PostgreSQL (and usually the whole server) has
> been re-started.
Maybe there's some firewall filtering that takes a while to start up
fully?
What I'd try to determine is whether this behavior occurs when PG itself
is restarted without rebooting the whole machine.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2009-10-20 14:57:57 | Re: Free Tool to design Postgres Databases |
Previous Message | Tom Lane | 2009-10-20 14:53:08 | Re: cast numeric with scale and precision to numeric plain |