[BUGS] Error connecting

2008-09-01 Thread Marcus Locatelli
So it just suddenly stopped working after 1 week for the 2nd time straight. The first time i reinstalled everything, lost database but it worked, now it just doesnt connect. What should i do? I use windows vista, run as administrator and everything

Re: [BUGS] libpq does not manage SSL callbacks properly when other libraries are involved.

2008-09-01 Thread Russell Smith
Alvaro Herrera wrote: > PoolSnoopy wrote: > >> ***PUSH*** >> >> this bug is really some annoyance if you use automatic build environments. >> I'm using phpunit to run tests and as soon as postgres is involved the php >> cli environment segfaults at the end. this can be worked around by disabling

[BUGS] Bug with FOR ... LOOP and composite types

2008-09-01 Thread Oleg Serov
Hello. Seems there is an error when I try to use a table with one field - composite type, when SELECT QUERY in FOR ... LOOP instruction returns empty result. Here are steps to reproduce: CREATE TYPE "t_type" AS ( "a" BIGINT ); CREATE TABLE"t_table" ( "id" BIGINT NOT NULL, "t" "t_type", CONSTRAIN

Re: [BUGS] Bug with FOR ... LOOP and composite types

2008-09-01 Thread Pavel Stehule
Hello 2008/9/1 Oleg Serov <[EMAIL PROTECTED]>: > Hello. > > Seems there is an error when I try to use a table with one field - composite > type, when SELECT QUERY in FOR ... LOOP instruction returns empty result. > Here are steps to reproduce: > > CREATE TYPE "t_type" AS ( > "a" BIGINT > ); > > CR

[BUGS] Bug in RETURN QUERY

2008-09-01 Thread Oleg Serov
Hello all SQL BUG CODE: BEGIN; SELECT version(); -- "PostgreSQL 8.3.3 on i686-redhat-linux-gnu, compiled by GCC gcc (GCC) 4.1.2 20070626 (Red Hat 4.1.2-14)" CREATE TYPE "buggy_enum_first" AS ENUM ( 'bug1', 'bug2', 'bug3' ); CREATE TABLE "bug_table" ( "id" BIGINT NOT NULL, "buggy_enum_field" "b

Re: [BUGS] libpq does not manage SSL callbacks properly when other libraries are involved.

2008-09-01 Thread Alvaro Herrera
Russell Smith wrote: > Alvaro Herrera wrote: > > PoolSnoopy wrote: > > > >> this bug is really some annoyance if you use automatic build environments. > >> I'm using phpunit to run tests and as soon as postgres is involved the php > >> cli environment segfaults at the end. this can be worked aro

Re: [BUGS] Bug in RETURN QUERY

2008-09-01 Thread Pavel Stehule
Hello 2008/9/1 Oleg Serov <[EMAIL PROTECTED]>: > Hello all SQL BUG CODE: > BEGIN; > SELECT version(); -- "PostgreSQL 8.3.3 on i686-redhat-linux-gnu, compiled by > GCC gcc (GCC) 4.1.2 20070626 (Red Hat 4.1.2-14)" > CREATE TYPE "buggy_enum_first" AS ENUM ( 'bug1', 'bug2', 'bug3' ); > > CREATE TABLE

[BUGS] BUG #4389: FATAL: could not reattach to shared memory (key=1804, addr=018E0000): 487

2008-09-01 Thread could not reattach to shared memory
The following bug has been logged online: Bug reference: 4389 Logged by: could not reattach to shared memory Email address: [EMAIL PROTECTED] PostgreSQL version: 8.3.3-1 Operating system: any 8.3.* Description:FATAL: could not reattach to shared memory (key=1804, add

Re: [BUGS] Bug with FOR ... LOOP and composite types

2008-09-01 Thread Tom Lane
"Pavel Stehule" <[EMAIL PROTECTED]> writes: > 2008/9/1 Oleg Serov <[EMAIL PROTECTED]>: >> Seems there is an error when I try to use a table with one field - composite >> type, when SELECT QUERY in FOR ... LOOP instruction returns empty result. > ROWTYPE is problem. I think it actually is a bug.

Re: [BUGS] Bug in RETURN QUERY

2008-09-01 Thread Tom Lane
"Pavel Stehule" <[EMAIL PROTECTED]> writes: > 2008/9/1 Oleg Serov <[EMAIL PROTECTED]>: >> ERROR: structure of query does not match function result type >> CONTEXT: PL/pgSQL function "buggy_procedure" line 3 at RETURN QUERY*/ > this isn't bug, it's feature. No, it's a bug, and it's not related t

Re: [BUGS] BUG #4389: FATAL: could not reattach to shared memory (key=1804, addr=018E0000): 487

2008-09-01 Thread Zdenek Kotala
could not reattach to shared memory napsal(a): The following bug has been logged online: Bug reference: 4389 Logged by: could not reattach to shared memory Email address: [EMAIL PROTECTED] PostgreSQL version: 8.3.3-1 Operating system: any 8.3.* Description:FATAL: co

Re: [BUGS] Bug with FOR ... LOOP and composite types

2008-09-01 Thread Oleg Serov
But if there are some records in t_table and we romove WHERE 1=0, we will have ERROR: wrong record type supplied in RETURN NEXT CONTEXT: PL/pgSQL function "t_func" line 9 at RETURN NEXT 2008/9/1 Pavel Stehule <[EMAIL PROTECTED]> > Hello > > 2008/9/1 Oleg Serov <[EMAIL PROTECTED]>: > > Hello. > >

[BUGS] BUG #4392: initdb doen't work with options -U username and -W

2008-09-01 Thread Andrea Villardino
The following bug has been logged online: Bug reference: 4392 Logged by: Andrea Villardino Email address: [EMAIL PROTECTED] PostgreSQL version: 8.3.3 Operating system: windows server 2003(or vista) Description:initdb doen't work with options -U username and -W Details

[BUGS] BUG #4391: initdb doen't work with options -U username and -W

2008-09-01 Thread Andrea Villardino
The following bug has been logged online: Bug reference: 4391 Logged by: Andrea Villardino Email address: [EMAIL PROTECTED] PostgreSQL version: 8.3.3 Operating system: windows server 2003(or vista). Description:initdb doen't work with options -U username and -W Detail

Re: [BUGS] Bug with FOR ... LOOP and composite types

2008-09-01 Thread Tom Lane
"Oleg Serov" <[EMAIL PROTECTED]> writes: > But if there are some records in t_table and we romove WHERE 1=0, we will > have > ERROR: wrong record type supplied in RETURN NEXT CONTEXT: PL/pgSQL function > "t_func" line 9 at RETURN NEXT I couldn't reproduce that here, at least not with versions newe

Re: [BUGS] Problem with planer

2008-09-01 Thread Russell Smith
[EMAIL PROTECTED] wrote: > select ats.id, ap.value from akh_test_suit ats > LEFT JOIN akh_properties ap on ap.ID = ats.test_suit_type_id > where ats.ID = 472 > > id | value > 472 | 472 > ID -- integer > value -- text > > > select * from akh_test_suit ats > LEFT JOIN akh_properties ap on ap.ID