| From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
|---|---|
| To: | petrovanster(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, PG Bug reporting form <noreply(at)postgresql(dot)org> |
| Subject: | Re: BUG #15161: libpq - Invalid SSPI context after PQreset |
| Date: | 2018-04-17 15:43:50 |
| Message-ID: | 148be035-0104-107d-c2bf-54bac530fde3@iki.fi |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 17/04/18 09:35, PG Bug reporting form wrote:
> PostgreSQL version: 9.3.5
>
> ...
>
> I've tried also changing the application to run a single thread and start 10
> instances of it. In this case there is no sspi error. Thus I suspect the
> libpq implementation.
The issue you're describing sounds a lot like the one that was fixed
here:
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=e6c33d594a004a2c831cdff1a16276347d30f703.
9.3.5 is a really old version. The latest 9.3 minor release is 9.3.22.
If what you're seeing is the same bug, it has been fixed in the latest
minor version. Even if it turns out to be something different, you
really need to upgrade.
Note: 9.3 major version is reaching end of life in September, so you
should start planning an upgrade to a more recent major version, too.
See https://www.postgresql.org/support/versioning/.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-04-18 01:59:10 | Re: BUG #15161: libpq - Invalid SSPI context after PQreset |
| Previous Message | Emre Hasegeli | 2018-04-17 15:14:05 | Re: Standby corruption after master is restarted |