rnysm...@yahoo.com writes:
> This month, we upgrade the libpq5 from 8.4.7 to 8.4.11.(libpq-dev
> 8.4.11-0ubuntu0.11.04) Our service program become unstable after upgrading.
It seems rather improbable that a deadlock inside glibc would be our
bug. Also, I've just looked very carefully through all
istvan.endr...@gmail.com writes:
> there is a table with 3000 rows, and a custom index with a function.
> This query gives negative cost:
> select distinct name
> from negativeCostBugReport t_
> where noaccent(t_.name) like 'B%' limit 10
Hm, interesting. The culprit seems to be the part of c
The following bug has been logged on the website:
Bug reference: 6579
Logged by: Istvan Endredy
Email address: istvan.endr...@gmail.com
PostgreSQL version: 9.1.3
Operating system: linux
Description:
Hi,
I've reduced the problem to this situation:
there is a tabl
The following bug has been logged on the website:
Bug reference: 6578
Logged by: Deadlock in libpq
Email address: rnysm...@yahoo.com
PostgreSQL version: 8.4.11
Operating system: Ubuntu 11.04
Description:
We wrote a C++ program using libpq to access postgres. it is a h
Hi,
more precisely the given index looks like this:
(to be able to repro the bug)
CREATE INDEX negativecostbugreport_noaccent_idx
ON negativeCostBugReport
USING btree
(noaccent(name) varchar_pattern_ops);
i'm sorry,
Istvan
No matter what numeric type I try to pass,(integer, numeric, currency) the ODBC
driver is turning it into "Double Precision"
Only If I send the value as a string
Declare nvar as numeric(10,2)
Nvar=1, nvar=1. or nvar=1.00 will come across as "Double Precision" input
bind variable.
Sending
Nvar
I'm running into the same issue here.
After install postgresql 9.1.2 and Activestate perl 5.14.2 execute:
create function perl_test() returns void as
$$
$$
language plperl
Generates server crash.
PostgreSQL version string: PostgreSQL 9.1.2, compiled by Visual C++ build
1500, 32 bit - Enterpris
