| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, obartunov(at)gmail(dot)com, Tomas Vondra <tv(at)fuzzy(dot)cz>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: jsonb and nested hstore |
| Date: | 2014-03-13 06:15:09 |
| Message-ID: | 20140313061509.GB8577@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 12, 2014 at 01:58:14PM -0700, Peter Geoghegan wrote:
> The use case you describe here doesn't sound like something similar to
> full text search. It sounds like something identical.
>
> In any case, let's focus on what we have right now. I think that the
> indexing facilities proposed here are solid. In any case they do not
> preclude working on better indexing strategies as the need emerges.
Keep in mind that if we ship an index format, we are going to have
trouble changing the layout because of pg_upgrade. pg_upgrade can mark
the indexes as invalid and force users to reindex, but that is less than
idea.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2014-03-13 09:21:49 | Re: jsonb and nested hstore |
| Previous Message | Bruce Momjian | 2014-03-13 05:48:58 | Re: pg_archivecleanup bug |