| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | CG <cgg007(at)yahoo(dot)com> |
| Cc: | "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org>, Dave Cramer <pg(at)fastcrypt(dot)com> |
| Subject: | Re: Upgrade to Scientific Linux 6.5 x86_64 breaks query |
| Date: | 2014-07-23 19:39:35 |
| Message-ID: | 25544.1406144375@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
CG <cgg007(at)yahoo(dot)com> writes:
> The question is what is causing valid SQL, prepared properly on 32bit linux to fail to prepare properly on 64bit linux? Based on that log, it looks like client-side prepare is falling down.
It seems quite unlikely that this is a 32-vs-64-bit problem, especially
given that you're working in Java and not something more
machine-dependent. I'd be looking at whether you have exactly the same
versions of the JDBC driver and other supporting libraries. One way or
another, the backend was getting told that $2 was an interval before,
and now it's not being told that.
Another possible reason for a behavioral discrepancy would be if you were
forcing PG protocol version 2 on one system and not the other.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sehrope Sarkuni | 2014-07-23 20:17:41 | Re: JBDC LDAP support for connection parameters |
| Previous Message | John R Pierce | 2014-07-23 19:33:09 | Re: Upgrade to Scientific Linux 6.5 x86_64 breaks query |