On 28/09/2020 14:26, Dmitry Yemanov wrote:
> 28.09.2020 13:27, Adriano dos Santos Fernandes wrote:
>
>> I would like something about cursors too and I think in the future it
>> can be added.
>
> I believe this should be a top-priority thing. I doubt many users
> implement heavy logic in PSQL without queries, so per-statement stats
> is mostly usable to quickly identify the slow query, for example. But
> the most interesting part comes after that - understand why query is
> slow. And here we need stats collected/shown per every plan node (at
> the RecordSource level). Obviously, RSB tree has no relation to source
> lines anymore, so it should be reported differently, RDB$PROFILE_STATS
> is not enough. I'd suggest to seriously think about that, as it may
> affect the design of the feature.
>

I have thought on that possibility since the start and the conflict
points I see are:
- Name of RDB$PROFILE_STATS - perhaps RDB$PROFILE_PSQL?
- New parameter(s) in START_SESSION specifying profile options - when
there are possible options

I see a need each time a system package is created to have:
- Named parameters (kind of Oracle =>), perhaps with :=
- Default parameters

Both things are very nice thing to have but the way it is, does not
break extensions (new parameters with DEFAULT added).

I do not mean it should (or should not) be integrated before
RecordSource profile, but that the design is not very impacted.


Adriano



Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

Reply via email to