| From: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
|---|---|
| To: | Eric Mortensen <eric(at)appstax(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: How jsonb updates affect GIN indexes |
| Date: | 2016-02-27 12:28:31 |
| Message-ID: | CA+bJJbxybXmKpxAS6uSFe9cKzAp6dd6y+E3r-azGdM+9pDG=Ng@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
CCing to list to maintain context.
On Sat, Feb 27, 2016 at 12:14 PM, Eric Mortensen <eric(at)appstax(dot)com> wrote:
> Thanks Francisco, I had not considered MVCC. If that is true, it would seem
> to me that a GIN index would "always" be less efficient, as it potentially
> would have to update every key's posting tree if a tuple moves, whereas two
> btree indexes would only require modififying two trees.
If you are that worried about performance, maybe your data will be
best served by splitting those fields out of the jsonb or even
splitting the table. As always, measure, identify bottleneck.
Francisco Olarte.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rafal Pietrak | 2016-02-27 17:19:17 | Re: multiple UNIQUE indices for FK |
| Previous Message | Francisco Olarte | 2016-02-27 11:00:03 | Re: How jsonb updates affect GIN indexes |