Demo Data from EDBT 2026 / reviewers in the wild / expert
Sasha Podolsky
dblp:385/5423
· DBLP profile ↗
1ranked-venue papers
0as first author
1since 2021 · last 2024
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Databases, data management, data science and information retrieval · 1 · 1 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
1 paper |
Indexing and storage engines · 38% Information retrieval · 38% Query processing and optimization · 12% |
Topics — the 4 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Information retrieval › similarity search
nearest neighbor search |
0.8 | 1 | 2024 | SingleStore-V: An Integrated Vector Database System in SingleStore · Proc. VLDB Endow. 2024 |
Indexing and storage engines
vector database |
0.8 | 1 | 2024 | SingleStore-V: An Integrated Vector Database System in SingleStore · Proc. VLDB Endow. 2024 |
Distributed and cloud data management › distributed database architecture
distributed relational database |
0.2 | 1 | 2024 | SingleStore-V: An Integrated Vector Database System in SingleStore · Proc. VLDB Endow. 2024 |
Query processing and optimization
SQL query processing |
0.2 | 1 | 2024 | SingleStore-V: An Integrated Vector Database System in SingleStore · Proc. VLDB Endow. 2024 |
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2024 | SingleStore-V: An Integrated Vector Database System in SingleStoreabstractVector databases have recently gained significant attention due to the emergence of large language models that produce vector embeddings for text. Existing vector databases can be broadly categorized into two types: specialized and generalized. Specialized vector databases are explicitly designed and optimized for managing vector data, while generalized ones support vector data management within a general purpose database. While specialized vector databases are interesting, there is a substantial customer base interested in generalized vector databases for various reasons, e.g., a reluctance to move data out of relational databases to reduce data silos and costs, the desire to use SQL, and the need for more sophisticated query processing of vector and non-vector data. However, generalized vector databases face two main challenges: performance and interoperability of vector search with SQL, such as combining vector search with filters, joins, or even fulltext search. In this paper, we present SingleStore-V, a full-fledged generalized vector database integrated into SingleStore, a modern distributed relational database optimized for both OLAP and OLTP workloads. SingleStore-V achieves high performance and interoperability via a suite of optimizations. Experiments on standard vector benchmarks show that SingleStore-V performs comparably to Milvus, a highly-optimized specialized vector database, and significantly outperforms pgvector, a popular generalized vector database in PostgreSQL. We believe this paper will shed light on integrating vector search into relational databases in general, as many design concepts and optimizations apply to other databases. Chenzhe Jin, Sasha Podolsky, Szu-Po Wang, Eric Hanson, Zhou Sun, Robert Walzer, Jianguo Wang 0001 |
Proc. VLDB Endow. | 4 |