To start with, it worked but the pg_hba.conf entry appeared to be wrong. I tried changing that and then the current problem started. I tried "listen_addresses = '*'"; then back to just 'localhost'.
Since I have maximum logging enabled, I don't think it is getting as far as reading the configuration files - that is not mentioned in the log.
There is no other instance of postgres running.
On 9 August 2013 00:59, Oliver Elphick <olly@xxxxxxxxxx> wrote:
To start with, it worked but the pg_hba.conf entry appeared to be wrong. I tried changing that and then the current problem started. I tried "listen_addresses = '*'"; then back to just 'localhost'.
Since I have maximum logging enabled, I don't think it is getting as far as reading the configuration files - that is not mentioned in the log.
There is no other instance of postgres running.On 9 August 2013 00:29, Adrian Klaver <adrian.klaver@xxxxxxxxx> wrote:On 08/08/2013 03:17 PM, Oliver Elphick wrote:What problems?
I tried to change the listen_addresses line in postgresql.conf, by
adding an IPv6 address. On meeting problems I tried changing it back.
Have you run ps to see if there is another instance of Postgres running?--
Currently it says:
listen_addresses = 'localhost'
Adrian Klaver
adrian.klaver@xxxxxxxxx
--
Time is short - http://www.lfix.co.uk/disappearance.html
Time is short - http://www.lfix.co.uk/disappearance.html
