| From: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Broken postgres links need to find callers [FIXED] |
| Date: | 2018-11-01 14:33:42 |
| Message-ID: | alpine.LNX.2.20.1811010728110.13759@salmo.appl-ecosys.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 31 Oct 2018, Rich Shepard wrote:
> I managed to mess up postgresql-10.3 on this Slackware-14.2 desktop
> server/workstation. It worked OK until I tried adding access to an another
> application.
The problems have been resolved by upgrading 10.3 to 10.5 using the
SlackBuild.org script. There was a minor error when that was changed from
version 9 to 10 and after correcting that the build went well. Long story
short: the server started and I can once again access databases using psql.
Now I go back to getting GRASS to connect to the database after modifying
postgresql.conf to accept connections from all hosts on my office network.
My thanks to Adrian and Andrew for their patient help.
Best regards,
Rich
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-11-01 14:35:40 | Re: backend crash on DELETE, reproducible locally |
| Previous Message | Vijaykumar Jain | 2018-11-01 14:07:47 | Re: incomplete startup packet messages in logs |