[
https://issues.apache.org/jira/browse/QPID-7974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209218#comment-16209218
]
Adel Boutros commented on QPID-7974:
------------------------------------
I have also in mind another minor enhancement:
We know that the tableExists is used in a single thread in the case of creating
all the needed Qpid tables. In that case, why don't we do a single getTables
and check in a single loop if all 6 tables exists in one shot? This way we save
5 redundant calls to getTables.
What do you think?
> JdbcUtils.TableExists is very slow on big databases such as Oracle
> ------------------------------------------------------------------
>
> Key: QPID-7974
> URL: https://issues.apache.org/jira/browse/QPID-7974
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: qpid-java-6.1.4
> Reporter: Adel Boutros
>
> The problem is that JdbcUtils.tableExists will actually load all tables and
> then iterate to find the correct one. On Oracle, this can be around 40 000
> tables. So it will take 12 minutes for the broker to start.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
