| From: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Simon Brooke <simon(at)weft(dot)co(dot)uk>, Postgres General mailing list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Linking legacy PHP stuff |
| Date: | 2000-08-20 00:56:01 |
| Message-ID: | 00081920573700.00745@lorc.wgcr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 18 Aug 2000, Tom Lane wrote:
> Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> writes:
> > At 6.4, there was a protocol change that renders clients for libpq
> > version 1 incapable of connecting or using servers using protocol
> > version 2. Thus, unless you want to do surgery on PHP/FI 2, you will
> > have to stick with PostgreSQL 6.3.2 or earlier.
> This is false (not to mention irrelevant to Simon's problem), because
> current servers still accept protocol version 1. What you cannot do
> at the moment is use a new libpq with an old server.
My error. However, I _have_ seen memory leaks and other problems with a client
that was statically linked with a pre-6.4 libpq on post 6.4 that worked
perfectly with pre-6.4 server.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lamar Owen | 2000-08-20 01:48:24 | Re: Linking legacy PHP stuff |
| Previous Message | The Hermit Hacker | 2000-08-20 00:49:34 | Re: 7.0.2 install doesn't read .conf files |