"Javier Hernandez" <[EMAIL PROTECTED]> writes:
> The following script generates an unexpected loss of connection.
I've applied a patch for this. Thanks for the report!
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to
Pedro Gimeno <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
> Here's a minimal test case:
> pruebas=# CREATE FUNCTION vc_gt(varchar,varchar) RETURNS boolean
> IMMUTABLE STRICT LANGUAGE SQL AS 'SELECT CAST($1 AS TEXT) > CAST($2 AS
> TEXT);';
> CREATE FUNCTION
> pruebas=# CREATE OPERATOR > (
>
Tom Lane wrote:
>> postgres=# select ''::varchar < ''::varchar;
>> ERROR: cache lookup failed for function 0
>
> Interesting. The symptom sounds vaguely familiar, though I can't find
> any relevant-looking CVS log entries right now. I'd suggest updating to
> 8.2.7 before you spend much time loo
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Javier Hernandez wrote:
>> select * from numeric_col_table where num_col in (select int_col from
>> int_col_table);
> So what's happening here is that it's writing the hash table using the
> wrong datatype ...
Yeah, the planner is at fault here --- it
Javier Hernandez wrote:
> select * from numeric_col_table where num_col in (select int_col from
> int_col_table);
#0 0x00752368 in pg_detoast_datum (datum=0x1)
at /pgsql/source/00head/src/backend/utils/fmgr/fmgr.c:2101
#1 0x006bf8bc in hash_numeric (fcinfo=0x7fffc5140550)
Ouch, crash confirmed --- studying the cause now.
---
Javier Hernandez wrote:
>
> The following bug has been logged online:
>
> Bug reference: 4113
> Logged by: Javier Hernandez
> Email address: [EMAIL P
The following bug has been logged online:
Bug reference: 4113
Logged by: Javier Hernandez
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.1
Operating system: Linux version 2.6.9-11.ELsmp; Red Hat 3.4.3-22; gcc
version 3.4.3
Description:server closed the conne
"Pedro Gimeno" <[EMAIL PROTECTED]> writes:
> I have an application running under Windows (tried both with XP and 2000)
> which when run, gets the server to a point in which every comparison of
> varchar < varchar gives the above error:
> postgres=# select ''::varchar < ''::varchar;
> ERROR: cache
"Prischepa Vladimir" <[EMAIL PROTECTED]> writes:
> I dump only one table which has mixed case name. But it doesn't work.
> It results in the following error:
> pg_dump.exe -h localhost -p 5433 -U postgres -i -F p -t '"T10441"' -v -f
> "test.sql" test
> pg_dump: No matching tables were found
Whi
Hello!
I dump only one table which has mixed case name. But it doesn't work.
It results in the following error:
pg_dump.exe -h localhost -p 5433 -U postgres -i -F p -t '"T10441"' -v -f
"test.sql" test
pg_dump: No matching tables were found
pg_dump: *** aborted because of error
Is that a bug o
The following bug has been logged online:
Bug reference: 4120
Logged by: Pedro Gimeno
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.5
Operating system: Debian Etch + Backports
Description:ERROR: cache lookup failed for function 0
Details:
I have an applic
Following my -general post about this issue I'm supplying a test case
for a query that fails with a 'Too many LWLocks held' error.
Thank you, I reproduced the bug and now I'm working on it.
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
[RESENT MESSAGE - the previous one was presumably held for moderation
because of an attachment. If the prior one did in fact make it through
and I just didn't get it then sorry for the noise.]
Hi all
Following my -general post about this issue I'm supplying a test case
for a query that fails with
13 matches
Mail list logo
