BUG #2790: constructor for int2vector seems to be buggy - Mailing list pgsql-bugs

From Gurjeet Singh
Subject BUG #2790: constructor for int2vector seems to be buggy
Date
Msg-id 200611281227.kASCRhQf077119@wwwmaster.postgresql.org
Whole thread Raw
Responses Re: BUG #2790: constructor for int2vector seems to be buggy
List pgsql-bugs
The following bug has been logged online:

Bug reference:      2790
Logged by:          Gurjeet Singh
Email address:      singh.gurjeet@gmail.com
PostgreSQL version: 8.2beta3
Operating system:   Windows
Description:        constructor for int2vector seems to be buggy
Details:

I couldn't find any documentation for the data type 'int2vector', so I
assume it is unsupported. And moreover, probably I am using an unsupported
syntax for populating it, so it may be not that high on priority.

But still filing, in case it uncovers something else.

    In the first INSERT statement, the array elements are separated by a
comma and a space; in the second one, the ones that are separated by just a
comma, do not get inserted!

    I could not reproduce it in standard inetegr arrays.

Session o/p:

postgres=# select version();
                                                version

----------------------------------------------------------------------------
----
------------------------
 PostgreSQL 8.2beta3 on i686-pc-mingw32, compiled by GCC gcc.exe (GCC) 3.2.3
(mi
ngw special 20030504-1)
(1 row)

postgres=# create table t ( a int2vector );
CREATE TABLE
postgres=# insert into t values ( '1, 2, 3' );
INSERT 0 1
postgres=# insert into t values ( '1,2,3, 4' );
INSERT 0 1
postgres=# select * from t;
   a
-------
 1 2 3
 1 4
(2 rows)

postgres=#

Best regards,

--
gurjeet[.singh]@EnterpriseDB.com
singh.gurjeet@{ gmail | hotmail | yahoo }.com

pgsql-bugs by date:

Previous
From: "Heikki Linnakangas"
Date:
Subject: Re: BUG #2784: Performance serious degrades over a period of a month
Next
From: "Thomas H."
Date:
Subject: Re: BUG #2781: database dump/restore problems