Skip site navigation (1) Skip section navigation (2)

Re: Postgresql array parser

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Aleksej Trofimov <aleksej(dot)trofimov(at)ruptela(dot)lt>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: Postgresql array parser
Date: 2011-12-13 14:17:48
Message-ID: (view raw or flat)
Lists: pgsql-novice
On Tue, Dec 13, 2011 at 3:16 AM, Aleksej Trofimov
<aleksej(dot)trofimov(at)ruptela(dot)lt> wrote:
> Hello, I wanted to ask according such a problem which we had faced with.
> We are widely using postgres arrays like key->value array by doing like
> this:
> {{1,5},{2,6},{3,7}}
> where 1,2,3 are keys, and 5,6,7 are values. In our pgSql functions we are
> using self written array_input(array::numeric[], key::numeric) function
> which makes a loop on whole array and searches for key like
> FOR i IN 1 .. size LOOP
>            if array[i][1] = key then
>                return array[i][2];
>            end if;
> But this was a good solution until our arrays and database had grown. So now
> FOR loop takes a lot of time to find value of an array.
> And my question is, how this problem of performance could be solved? We had
> tried pgperl for string parsing, but it takes much more time than our
> current solution. Also we are thinking about self-written C++ function, may
> be someone had implemented this algorithm before?

A better way to do a brute force loop of arrays came along in 9.1:

A slightly smarter lookup could be done if you were willing to make a
key, value composite type like so:
postgres=# create type pair as (key text, value text);

postgres=# select array[row('a', 'b'), row('c', 'd')]::pair[];
(1 row)

postgres=# select * from (select unnest( array[row('a', 'b'), row('c',
'd')]::pair[]) as pair) q where (pair).key = 'a';
(1 row)

postgres=# select (pair).* from (select unnest( array[row('a', 'b'),
row('c', 'd')]::pair[]) as pair) q where (pair).key = 'a';
 key | value
 a   | b
(1 row)

However, if you are managing large key-value lists though you really
should either A. looking at hstore (hstore is a generalization of
key/value storage in a single column and supports GIST/GIN for

or B. normalizing your structure (why have you not already done this?).


In response to

pgsql-novice by date

Next:From: DFEDate: 2011-12-13 14:30:18
Subject: pgagent linux 64bit
Previous:From: Pandu PoluanDate: 2011-12-13 11:38:08
Subject: Re: SELECT from two tables with different field names?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group