From: | Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | Sam Mason <sam(at)samason(dot)me(dot)uk>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: newbie table design question |
Date: | 2009-06-02 13:33:46 |
Message-ID: | 2f4958ff0906020633i1b5caa10wd65a15467fd44a5f@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Jun 2, 2009 at 2:27 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> _IF_ arrays fit your requirements, they are an extremely compact and
> efficient way to store your data. The requirements are exact..you
> can't update or extract a single piece of data out of a block
> efficiently. While indexing techniques are possible with gist, they
> are moderate help at best. But if arrays fit, your table will be a
> fraction of size of the 'row per datum' approach, at the cost of
> flexibility. arrays are an enormous footgun when used in tables, but
> if used properly can work well.
Gin index works with arrays too.
--
GJ
From | Date | Subject | |
---|---|---|---|
Next Message | Carlos Oliva | 2009-06-02 13:34:15 | Schema, database, or tables in different folders? |
Previous Message | Martin Gainty | 2009-06-02 13:32:31 | Re: Query timeout in dbcp |