[arch-general] Postgres failure after system upgrade

[mario.stg at sympatico.ca]

Hi.  Check this thread http://bbs.archlinux.org/viewtopic.php?id=48525. 
Same story goes on there.  There is a link for downgrading.


On Wed, May 14, 2008 5:53 pm, richard terry wrote:
> On Thu, 15 May 2008 07:57:58 am you wrote:
> Oh my god! Does that mean all my data is screwed? (Of course I've
> backups). Can I downgrade somehow???
>
>
> regards
>
> Richard
>
>
>> On Wed, May 14, 2008 at 4:45 PM, richard terry <rterry at gnumed.net>
>> wrote:
>>
>>> Yesterday upgraded my system which happened to include I think from
>>> memory as well as postgres 8.3 , php.
>>>
>>> Not a technical person unfortunately, but my postgres has died with
>>> the message  below.
>>>
>>> I wonder if some kind soul could give me some help in tracking down
>>> the problem. I've tried looking at the below mentioned files and can't
>>> see anything wrong . Perhaps something got overwritten?
>>>
>>> An help appreciated.
>>>
>>>
>>> Richard
>>>
>>>
>>>
>>> The server doesn't accept connections: the connection library reports
>>>  could not connect to server: Connection refused Is the server
>>> running on host "127.0.0.1" and accepting TCP/IP connections on port
>>> 5432?
>>> If you encounter this message, please check if the server you're
>>> trying to contact is actually running PostgreSQL on the given port.
>>> Test if you
>>> have network connectivity from your client to the server host using
>>> ping or equivalent tools. Is your network / VPN / SSH tunnel /
>>> firewall configured correctly? For security reasons, PostgreSQL does
>>> not listen on all available IP addresses on the server machine
>>> initially. In order to access the server over the network, you need to
>>> enable listening on the address first. For PostgreSQL servers starting
>>> with version 8.0, this is controlled using the "listen_addresses"
>>> parameter in the postgresql.conf file. Here, you can enter a list of
>>> IP addresses the server should listen on, or
>>> simply use '*' to listen on all available IP addresses. For earlier
>>> servers (Version 7.3 or 7.4), you'll need to set the "tcpip_socket"
>>> parameter to 'true'. You can use the postgresql.conf editor that is
>>> built into pgAdmin III to edit the postgresql.conf configuration file.
>>> After
>>> changing this file, you need to restart the server process to make the
>>>  setting effective. If you double-checked your configuration but still
>>> get this error message, it's still unlikely that you encounter a fatal
>>> PostgreSQL
>>> misbehaviour. You probably have some low level network connectivity
>>> problems (e.g. firewall configuration). Please check this thoroughly
>>> before reporting a bug to the PostgreSQL community.
>>
>> Same thing here?
>> http://bugs.archlinux.org/task/10401
>>
>
>