Activity
From 10/06/2020 to 11/04/2020
11/04/2020
- 12:43 PM Feature #4996 (WIP): Integrate hash indexes in H2 temp-tables
- 09:24 AM Bug #4994: NPE in AdaptiveQuery when loading null data for an outer join
- When a @CompoundQuery@ has a component using the OUTER JOIN option, we try to load data via the @AdaptiveQuery.load(O...
- 09:13 AM Bug #4994 (Closed): NPE in AdaptiveQuery when loading null data for an outer join
- 03:53 AM Feature #4055: optimize temp-table output parameter copying
- Regarding @optimize extent bulk copy using insert into select from@, I found an optimization which doesn't rely anymo...
10/30/2020
- 01:14 PM Feature #1587: implement full support for word indexes
- The @TEMP-TABLE:ADD-NEW-INDEX@ method depends on this, as noted in #4397. When task is finished, the word indexes mus...
- 01:05 PM Feature #4397: add database attrs, methods and options
- >> TEMP-TABLE:ADD-NEW-INDEX() method
>
> Not touched. (It is currently marked as partial because it doesn't handle ... - 11:53 AM Feature #4397: add database attrs, methods and options
- Status of issues in 4397a/11776.
> * @BUFFER:LAST-BATCH@ attribute
Done 99%. There is one edge-case where a "look-a... - 07:12 AM Feature #4055: optimize temp-table output parameter copying
- Directions for temp-table copy optimization:
* -extend the use of *insert into select from* for some cases of append... - 07:08 AM Feature #4055: optimize temp-table output parameter copying
- *Extent*: When in @insertBulk@ mode, the extents fields are copied one by one. This can be also optimized with a @in...
10/29/2020
- 12:11 PM Feature #4055: optimize temp-table output parameter copying
- I will ignore #4055-60 for now, it doesn't fit my understanding of how @copy-temp-table@ is working. I will document ...
- 07:06 AM Feature #4055: optimize temp-table output parameter copying
- I am a bit confused of two recently generated testcases. I tried to experiment with @copy-temp-table@ in the context ...
- 05:34 AM Feature #4055: optimize temp-table output parameter copying
- Eric Faulhaber wrote:
> Each legacy temp-table index, whether it is unique or not in the legacy schema, is created w...
10/28/2020
- 02:02 PM Feature #4055: optimize temp-table output parameter copying
- Insofar as this affects your design decisions, please note that we do not actually create unique indices for temp-tab...
10/27/2020
- 08:42 AM Feature #4055: optimize temp-table output parameter copying
- I have experimented some scenarios both in 4GL and FWD and I wanted to point out some hot-spots and maybe some optimi...
10/26/2020
- 09:46 AM Feature #1587: implement full support for word indexes
- Creates task branch 1587a
10/23/2020
- 11:22 AM Feature #4980 (New): Investigate the impact of TOAST manipulation in PotgreSQL engine
- PostgreSQL has a manager (named TOAST) which ensures that all texts wider than TOAST_TUPLE_THRESHOLD (usually 2kB) ar...
10/20/2020
- 01:21 PM Bug #4825: OutputTableHandleCopier dynamically defines destination temp-table
- Attached is the patch which instruments the @OutputTableHandleCopier.finished@ method via JMX bean.
10/19/2020
- 04:29 PM Bug #4825: OutputTableHandleCopier dynamically defines destination temp-table
- Eric Faulhaber wrote:
> A useful first step to help prioritize this optimization would be to instrument this code ...
10/15/2020
- 02:50 AM Bug #4945: Optimize indexes for H2 dialect
- Ovidiu, there is no H2 dedicated repository yet. My patch on H2 is not safe, so I didn't worry about a repository jut...
10/14/2020
- 07:12 PM Bug #4945: Optimize indexes for H2 dialect
- I finished the solution for avoiding re-sorting the data if a reversed index is detected. I have chosen the solution ...
10/09/2020
- 05:20 PM Bug #4945: Optimize indexes for H2 dialect
- Eric Faulhaber wrote:
> OK, as soon as you are comfortable with your FWD-only changes, please commit them.
Done, se... - 04:40 PM Bug #4945: Optimize indexes for H2 dialect
- OK, as soon as you are comfortable with your FWD-only changes, please commit them.
As to the H2 changes, please DO... - 04:27 PM Bug #4945: Optimize indexes for H2 dialect
- I will answer in reverse order.
> Is the first item in #4945-15 something that stands on its own?
Yes, I adjusted... - 03:53 PM Bug #4945: Optimize indexes for H2 dialect
- Ovidiu, do you expect to have any update today? Is the first item in #4945-15 something that stands on its own?
10/08/2020
- 06:36 PM Bug #4945: Optimize indexes for H2 dialect
- Constantin Asofiei wrote:
> Without the @_multiplex@ first at the ORDER BY, the WHERE will choose a different index;...
10/07/2020
- 01:43 AM Bug #4945: Optimize indexes for H2 dialect
- Eric Faulhaber wrote:
> Constantin, do you remember why we moved @_multiplex@ to the front of index definitions and ... - 01:40 AM Bug #4945: Optimize indexes for H2 dialect
- From my debugging of the AdaptiveQuery, in H2 the LIMIT is applied at the fetch, and not after re-sort, if the fetch ...
10/06/2020
- 05:40 PM Bug #4945: Optimize indexes for H2 dialect
- Ovidiu Maxiniuc wrote:
> Eric Faulhaber wrote:
> > Are you talking about H2 changes here, or just FWD changes?
> T... - 05:27 PM Bug #4945: Optimize indexes for H2 dialect
- When H2 selects the index @Select.getSortIndex()@ it looks for the first N components of the index to be a perfect ma...
- 05:03 PM Bug #4945: Optimize indexes for H2 dialect
- Constantin, do you remember why we moved @_multiplex@ to the front of index definitions and ORDER BY clauses? I origi...
- 05:00 PM Bug #4945: Optimize indexes for H2 dialect
- Eric Faulhaber wrote:
> Are you talking about H2 changes here, or just FWD changes?
There are two set of changes:
... - 04:17 PM Bug #4945: Optimize indexes for H2 dialect
- Ovidiu Maxiniuc wrote:
> Eric Faulhaber wrote:
> > But will this mean H2 will select the index AND not re-sort afte... - 03:36 PM Bug #4945: Optimize indexes for H2 dialect
- Ovidiu Maxiniuc wrote:
> Constantin Asofiei wrote:
> > What happens if the index in 4GL is originally as @index ix1... - 01:20 PM Bug #4945: Optimize indexes for H2 dialect
- Another issue I noticed while debugging: there was an extra index, having the @recid@ as unique component. It was mar...
- 01:11 PM Bug #4945: Optimize indexes for H2 dialect
- Eric Faulhaber wrote:
> But will this mean H2 will select the index AND not re-sort after the results are fetched? O... - 01:07 PM Bug #4945: Optimize indexes for H2 dialect
- Constantin Asofiei wrote:
> What happens if the index in 4GL is originally as @index ix1 f1 desc@?
Evidently, the... - 12:27 PM Bug #4945: Optimize indexes for H2 dialect
- Ovidiu Maxiniuc wrote:
> Right. I am adding now the @DESC@ direction to @_multiplex@ when FWD detects a reversed i... - 12:25 PM Bug #4945: Optimize indexes for H2 dialect
- What happens if the index in 4GL is originally as @index ix1 f1 desc@?
- 12:24 PM Bug #4945: Optimize indexes for H2 dialect
- Constantin Asofiei wrote:
> I don't understand - what's the exact @ORDER BY@ clause? Do you mean there is an @ORDER... - 12:13 PM Bug #4945: Optimize indexes for H2 dialect
- Ovidiu Maxiniuc wrote:
> * I discovered a bug in FWD related to sorting temp-tables queries. When a reversed order i... - 11:18 AM Bug #4945: Optimize indexes for H2 dialect
- I took a look over H2 code that handles selection of the index (@Select.prepare()@)to be used for a query and the pos...
- 10:54 AM Bug #4945: Optimize indexes for H2 dialect
- We notice that sometimes the temp-table queries are slow because the matching reversed index is not selected by the q...
- 10:48 AM Bug #4945 (Feedback): Optimize indexes for H2 dialect
Also available in: Atom