2021
DOI: 10.1007/978-3-030-72651-5_46
|View full text |Cite
|
Sign up to set email alerts
|

Comparing Oracle and PostgreSQL, Performance and Optimization

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2022
2022
2023
2023

Publication Types

Select...
3
1

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(1 citation statement)
references
References 12 publications
0
1
0
Order By: Relevance
“…Taking the same input, i.e., a query statement, the latter uses the query plan tree [21] generated by the optimizer of a DBMS to estimate the query cardinality. It is worth noting that this method does not require the execution of query statements in the database and is efficient, as DBMS uses traditional estimation methods to obtain plans [22]. Although these plans may be suboptimal, we can use the information embedded in them for cardinality estimation.…”
Section: Introductionmentioning
confidence: 99%
“…Taking the same input, i.e., a query statement, the latter uses the query plan tree [21] generated by the optimizer of a DBMS to estimate the query cardinality. It is worth noting that this method does not require the execution of query statements in the database and is efficient, as DBMS uses traditional estimation methods to obtain plans [22]. Although these plans may be suboptimal, we can use the information embedded in them for cardinality estimation.…”
Section: Introductionmentioning
confidence: 99%