Re: problem with partitioned table and indexed json field
От | Raphael Bauduin |
---|---|
Тема | Re: problem with partitioned table and indexed json field |
Дата | |
Msg-id | CAONrwUEvOcajRCTA8ypB2XSQPfTub50rekSPZOt9D9E4ZAcuUw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: problem with partitioned table and indexed json field (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: problem with partitioned table and indexed json field
|
Список | pgsql-general |
The query is also problematic here, because it returns the full json, and not only the data I selected in the json.
Below, it should return only '_id', and not the whole json stored in event:
test3=> select max(event->>'_id') from events where event is not null;
max
------------------------------------------------
{"_id":"5f93c3a044650105b5074c9a","type":"t2"}
Thanks
raph
Below, it should return only '_id', and not the whole json stored in event:
test3=> select max(event->>'_id') from events where event is not null;
max
------------------------------------------------
{"_id":"5f93c3a044650105b5074c9a","type":"t2"}
Thanks
raph
On Thu, Nov 7, 2013 at 4:32 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Raphael Bauduin <rblists@gmail.com> writes:Thanks, I've reproduced the problem here. The query still seems to run OK,
> I have narrowed it a bit. It happens when I create said index on an empty
> field. Here's the scenario to reproduce it:
it's just EXPLAIN that's falling over --- do you see the same?
regards, tom lane
--
Web database: http://www.myowndb.com
Free Software Developers Meeting: http://www.fosdem.org
В списке pgsql-general по дате отправления: