| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andrus <kobruleht2(at)hot(dot)ee> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: How to fix 0xC0000005 exception in Postgres 9.0 |
| Date: | 2020-02-20 22:49:39 |
| Message-ID: | 21459e71-77c1-c3d0-a3e4-e2b97fd1efc3@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2/20/20 2:42 PM, Alvaro Herrera wrote:
> On 2020-Feb-20, Andrus wrote:
>
>>> Upgrade to a version of Postgres that is not 5 years past EOL?
>>
>> Not possible at moment because requires lot of testing not to break existing
>> applications.
>> Planned in future.
>
> Applications are already broken, since they can't connect, right? Seems
> like a great time to test them with an upgraded server.
>
Realized I should have been clearer. By pre-libpq I meant this:
https://odbc.postgresql.org/docs/release.html
psqlODBC 09.05.0100 Release
Changes:
Use libpq for all communication with the server
Previously, libpq was only used for authentication. Using it for
all communication lets us remove a lot of duplicated code. libpq is now
required for building or using libpq.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2020-02-20 22:50:56 | Re: How to fix 0xC0000005 exception in Postgres 9.0 |
| Previous Message | Ron | 2020-02-20 22:48:38 | Re: How to fix 0xC0000005 exception in Postgres 9.0 |