On Thu, Nov 7, 2013 at 7:24 PM, Tom Lane t...@sss.pgh.pa.us wrote:
I wrote:
It looks like the problem is we're building a MergeAppend plan and not
getting the targetlist for the MergeAppend node right.
Found it --- simple oversight in building optimized min/max plans.
If you need a patch
Hi,
I have narrowed it a bit. It happens when I create said index on an empty
field. Here's the scenario to reproduce it:
Let me know if you need more info
Cheers
Raph
create table events(id SERIAL,
timestamp timestamp,
event json);
create table
Correction: It happens when I create said index on an empty *table*.
Raph
On Thu, Nov 7, 2013 at 11:10 AM, Raphael Bauduin rbli...@gmail.com wrote:
Hi,
I have narrowed it a bit. It happens when I create said index on an empty
field. Here's the scenario to reproduce it:
Let me know if you
Raphael Bauduin rbli...@gmail.com writes:
I have narrowed it a bit. It happens when I create said index on an empty
field. Here's the scenario to reproduce it:
Thanks, I've reproduced the problem here. The query still seems to run OK,
it's just EXPLAIN that's falling over --- do you see the
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
Raphael Bauduin rbli...@gmail.com writes:
The query is also problematic here, because it returns the full json, and
not only the data I selected in the json.
Doh, right, you mentioned that in the original bug report, and now that
I'm paying a bit more attention I see it too. I was looking for
I wrote:
It looks like the problem is we're building a MergeAppend plan and not
getting the targetlist for the MergeAppend node right.
Found it --- simple oversight in building optimized min/max plans.
If you need a patch now, see
I'll look at providing such an example later this week.
Raph
On Thu, Oct 31, 2013 at 3:23 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Raphael Bauduin rbli...@gmail.com writes:
An explain returns an error:
= explain select max(event-'_id') from events;
ERROR: no tlist entry for key 2
This
Hi,
I have a partitioned table events, with one partition for each month, eg
events_2013_03. The partition is done on the field timestamp, and
constraints are set, but insertion of data is done in the partition
directly (so not with a trigger on the events table)
The field event is of type json,
On Thu, Oct 31, 2013 at 5:46 AM, Raphael Bauduin rbli...@gmail.com wrote:
Hi,
I have a partitioned table events, with one partition for each month, eg
events_2013_03. The partition is done on the field timestamp, and
constraints are set, but insertion of data is done in the partition
It's postgresql 9.3, from the pgdg apt repository:
9.3.0-2.pgdg10.4+1
Raph
On Thu, Oct 31, 2013 at 1:48 PM, Merlin Moncure mmonc...@gmail.com wrote:
On Thu, Oct 31, 2013 at 5:46 AM, Raphael Bauduin rbli...@gmail.com
wrote:
Hi,
I have a partitioned table events, with one partition for
Raphael Bauduin rbli...@gmail.com writes:
An explain returns an error:
= explain select max(event-'_id') from events;
ERROR: no tlist entry for key 2
This is certainly a bug. Can we see a self-contained example that
triggers that?
regards, tom lane
--
Sent via
12 matches
Mail list logo
