Not yet. I would first like to know what is the time consuming part and
what is a work around. If you are sure individual columns for every
entry of the array solve the issue I will joyfully implement it. The
downsize of this approch is that the array dimensions are not always the
same in my scena
On Wed, Jun 21, 2006 at 09:29:03AM +0200, Merkel Marcel (CR/AEM4) wrote:
>
>
> Von: Merlin Moncure [mailto:[EMAIL PROTECTED]
> An: Merkel Marcel (CR/AEM4)
> Cc: pgsql-performance@postgresql.org
> Betreff: Re: [PERFORM] Big array speed issues
>
> On 6/20/06, Merkel
Von: Merlin Moncure [mailto:[EMAIL PROTECTED]
An: Merkel Marcel (CR/AEM4)
Cc: pgsql-performance@postgresql.org
Betreff: Re: [PERFORM] Big array speed issues
On 6/20/06, Merkel Marcel (CR/AEM4) <[EMAIL PROTECTED]> wrote:
> I use libpqxx to access the database. This might be another
b
On 6/20/06, Merkel Marcel (CR/AEM4) <[EMAIL PROTECTED]> wrote:
I use libpqxx to access the database. This might be another bottleneck, but
I assume my query and table setup is the bigger bottleneck. Would it make
sense to fetch the whole array ? (Select map from table where … and parse
the arra
Title: Big array speed issues
Hi,
I have some speed issues with a big array in a table. I hope you can help me to tune my query.
My table looks like this:
Id | timestamp | map
Primary key | timestamp | array of real [34][28]
With an index on timestamp
My query
