Demo Data from EDBT 2026 / reviewers in the wild / expert
Jaeseon Yu
dblp:266/5863
· DBLP profile ↗
3ranked-venue papers
0as first author
2since 2021 · last 2022
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Databases, data management, data science and information retrieval · 3 · 2 since 2021
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Databases, data mining, and information retrieval
3 papers |
Transaction processing and concurrency control · 69% Indexing and storage engines · 20% Database system architecture and tuning · 11% |
Topics — the 9 heaviest of 9, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Transaction processing and concurrency control › concurrency control
multiversion concurrency control |
1.2 | 3 | 2022 | Diva: Making MVCC Systems HTAP-Friendly · SIGMOD Conference 2022 Long-lived Transactions Made Less Harmful · SIGMOD Conference 2020 Rethink the Scan in MVCC Databases · SIGMOD Conference 2021 |
Database system architecture and tuning
hybrid transactional and analytical processing |
0.6 | 1 | 2022 | Diva: Making MVCC Systems HTAP-Friendly · SIGMOD Conference 2022 |
Transaction processing and concurrency control › versioning
version storage |
0.6 | 1 | 2022 | Diva: Making MVCC Systems HTAP-Friendly · SIGMOD Conference 2022 |
Indexing and storage engines
access methods |
0.5 | 1 | 2021 | Rethink the Scan in MVCC Databases · SIGMOD Conference 2021 |
Indexing and storage engines
multiversion index |
0.5 | 1 | 2021 | Rethink the Scan in MVCC Databases · SIGMOD Conference 2021 |
Transaction processing and concurrency control › concurrency control › multiversion concurrency control
garbage collection |
0.4 | 1 | 2020 | Long-lived Transactions Made Less Harmful · SIGMOD Conference 2020 |
Transaction processing and concurrency control › transaction models
long-lived transactions |
0.4 | 1 | 2020 | Long-lived Transactions Made Less Harmful · SIGMOD Conference 2020 |
Transaction processing and concurrency control › isolation levels
snapshot isolation |
0.4 | 1 | 2020 | Long-lived Transactions Made Less Harmful · SIGMOD Conference 2020 |
Transaction processing and concurrency control
versioning |
0.4 | 1 | 2020 | Long-lived Transactions Made Less Harmful · SIGMOD Conference 2020 |
Methods — techniques the papers use, named apart from their topics
time interval-based garbage collection · 0.6decoupled version index · 0.6version search structure · 0.5pointer augmentation · 0.5
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2022 | Diva: Making MVCC Systems HTAP-FriendlyabstractMultiversion concurrency control (MVCC) and design principles thereof are ingrained in modern database management systems, thus promoting remarkable progress in managing online transaction processing (OLTP) workloads for decades. However, MVCC systems would battle two vital concerns when facing hybrid transactional/analytical processing (HTAP). The first concern is to ensure rapid version searching for analytic queries with less I/O, and the second concern is to reclaim garbage data versions promptly for easing the strain on storage footprint. These are often tightly coupled since many MVCC systems rely on unified version storage that poses a space-time tradeoff in HTAP, giving rise to disappointing performance metrics that may negatively stereotype OLTP-friendly MVCC systems. This paper refutes the stereotype resulting from coupled design concerns and addresses the core problem by proposing Diva (Decoupling Index from Version dAta) that physically separates version index from version data; for decoupled concerns, we devise independent management policies: provisional version indexing and time interval-based version garbage collection. The separation of coupled concerns would render legacy disk-based MVCC systems more HTAP-friendly. We applied Diva to two full-fledged database systems---PostgreSQL and MySQL---and demonstrated that the systems with Diva escaped the space-time tradeoff under hybrid transactional/analytical workloads. Jong-Bin Kim, Jaeseon Yu, Jaechan Ahn, Sooyong Kang, Hyungsoo Jung 0001 |
SIGMOD Conference | 2 |
| 2021 | Rethink the Scan in MVCC DatabasesabstractA scan is one of the fundamental operations in databases for retrieving tuples from tables, and research on access methods has been of importance to query optimization. However, our community is aware of the inconvenient truth that its performance may plummet amid steep increases in search costs when acting on MVCC databases since multi-versioning may forfeit all the benefits of using database indexes. An execution plan for a query on multi-versioned data often comprises a series of point lookup operations, of which each internally executes a linear traversal of record versions. Therefore, the generated plan is surprisingly worse than a full table (or version store) scan, mainly due to redundant access to database pages. To address such an all-or-nothing approach, we propose version weaver (vWeaver), a light-weight access method for record versions, that expedites a scan on record versions with each being augmented by just a few pointer fields. vWeaver incrementally constructs a version search structure over even an append-only version store (e.g., undo space) and allows a scan to traverse new version search structures for fast lookup. We applied vWeaver to in-memory and disk-based MVCC databases and demonstrated that the systems with vWeaver generally improved scan performance under various workloads with negligible space overhead. Jong-Bin Kim, Kihwang Kim, Hyunsoo Cho, Jaeseon Yu, Sooyong Kang, Hyungsoo Jung 0001 |
SIGMOD Conference | 4 |
| 2020 | Long-lived Transactions Made Less HarmfulabstractMany systems use snapshot isolation, or something similar, as defaults, and multi-version concurrency control (MVCC) remains essential to offering such point-in-time consistency. One major issue in MVCC is the timely removal of unnecessary versions of data items, especially in the presence of long-lived transactions (LLTs). We have observed that the latest versions of MySQL and PostgreSQL are still vulnerable to LLTs. Our analysis of existing proposals suggests that new solutions to this matter must provide rigorous rules for completely identifying unnecessary versions, and elaborate designs for version cleaning lest old versions required for LLTs should suspend garbage collection. In this paper, we formalize such rules into our version pruning theorem and version classification, of which all form theoretical foundations for our new version management system, vDriver, that bases its record versioning on a new principle: Single In-row Remaining Off-row (SIRO) versioning. We implemented a prototype of vDriver and integrated it with MySQL-8.0 and PostgreSQL-12.0. The experimental evaluation demonstrated that the engines with Driver continue to perform the reclamation of dead versions in the face of LLTs while retaining transaction throughput with reduced space consumption. Jong-Bin Kim, Hyunsoo Cho, Kihwang Kim, Jaeseon Yu, Sooyong Kang, Hyungsoo Jung 0001 |
SIGMOD Conference | 4 |