You guys are smart!
Apache was running against an old libpq. I shutdown apache, updated
/etc/ld.so.conf with the postgres lib dir, ran ldconfig, restarted
apache, and the problem went away.
The old libpq was libpq.so.3.0 (pre-installed on machine). The new one
is libpq.so.3.2 (installed wi
On Thu, Feb 09, 2006 at 12:46:46PM -0300, Alvaro Herrera wrote:
> I note in the PHP 4 sources that the PQunescapeBytea function seems to
> have been copied there, "for the benefit of PostgreSQL 7.2 users". It
> says that it comes from 7.3 but I don't see any sscanf call.
>
> There is no PQunescap
> The following bug has been logged online:
>
> Bug reference: 2248
> Logged by: Fix for terminal server
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.2
> Operating system: Win 32
> Description:Fix for terminal server
> Details:
>
> I am sorry, these i
Tom Lane wrote:
> Kalador Tech Support <[EMAIL PROTECTED]> writes:
> > When run from a browser, accessing an Apache webserver, the results
> > displayed were:
>
> > fetchtime = 3.632ms, 296043 bytes
> > unescape time = 70625.518ms, 296043 bytes
>
> Is it possible that you are relying on an o
On Thu, 9 Feb 2006, Satheesh wrote:
The following bug has been logged online:
Bug reference: 2249
PostgreSQL version: 7.3.2
Description:unsupported frontend protocol
Details:
iam having database server postgres version 7.3.2 and jboss 4.x as
webserver, while executing the appli
"Satheesh" <[EMAIL PROTECTED]> writes:
> iam having database server postgres version 7.3.2 and jboss 4.x as
> webserver, while executing the application iam getting an error message of
> "FATAL:Unsupported Front end Protocol". This makes my application to execute
> slowly. plz help me. Tahnks in Ad
Kalador Tech Support <[EMAIL PROTECTED]> writes:
> When run from a browser, accessing an Apache webserver, the results
> displayed were:
> fetchtime = 3.632ms, 296043 bytes
> unescape time = 70625.518ms, 296043 bytes
Is it possible that you are relying on an old (like 7.3) libpq?
I find this
On 2006-02-08, Matej Rizman <[EMAIL PROTECTED]> wrote:
> No.
>
> But the similar problem first appeared on tables that are on
> production servers and VACUUMed regularly (in addition to autovacuum).
>
> The same problem appears if tables are created with SELECT INTO and
> with indices created latte
The following bug has been logged online:
Bug reference: 2248
Logged by: Fix for terminal server
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.2
Operating system: Win 32
Description:Fix for terminal server
Details:
I am sorry, these is not a bug report bu
2006/2/8, Bruno Wolff III <[EMAIL PROTECTED]>:
> On Tue, Feb 07, 2006 at 02:41:03 +,
> Matej Rizman <[EMAIL PROTECTED]> wrote:
> >
> > Files a_3.txt and b_3.txt contain 3 numbers each.
> >
> > The last query (SELECT) is executed on my machine in 125ms.
> >
> > If I load data from
The following bug has been logged online:
Bug reference: 2250
Logged by: Ian Moore
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: Windows XP
Description:JSTL parameterized queries inserting numeric values
Details:
When using the JSTL vi
I modified your code slightly to isolate the pg_unescape_bytea() from
the pg_fetch_result():
When run from a browser, accessing an Apache webserver, the results
displayed were:
fetchtime = 3.632ms, 296043 bytes
unescape time = 70625.518ms, 296043 bytes
When running the same code from c
The following bug has been logged online:
Bug reference: 2249
Logged by: Satheesh
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.3.2
Operating system: Red hat Linux 9
Description:unsupported frontend protocol
Details:
hi,
iam having database server postgres
The following bug has been logged online:
Bug reference: 2247
Logged by: Tatiana Gribanovskaia
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8
Operating system: Linux
Description:Old Postgres driver
Details:
We have a website which is running on Postgres 8 da
On Thu, Feb 09, 2006 at 04:22:26AM +, shyam nair wrote:
> Now I have a situation like the sequence id is repeating. This
> applicaton is running since from 1999, this is the first time we
> get such a result.
What version of PostgreSQL are you running? Hopefully you've
upgraded since 1999.
15 matches
Mail list logo