yugabyte/yugabyte-db

[YSQL] Investigate read time logic for unique key violation

Open

#27,083 opened on May 7, 2025

View on GitHub
 (1 comment) (0 reactions) (1 assignee)C (1,003 forks)batch import
area/ysqlgood first issuekind/enhancementpriority/mediumstatus/awaiting-triage

Repository metrics

Stars
 (8,229 stars)
PR merge metrics
 (Avg merge 17d 21h) (92 merged PRs in 30d)

Description

Jira Link: DB-16570

Description

Motivation: pg compatibility (and improve availability by reducing serialization errors).

As part of this task,

  1. Verify the snapshot using which postgres detects unique key violations. See _bt_check_unique.
  2. Verify whether YB implements the same snapshot mechanism for detecting unique key violations. See pgsql_operation.cc
  3. Match pg behavior.

Issue Type

kind/enhancement

Warning: Please confirm that this issue does not contain any sensitive information

  • I confirm this issue does not contain any sensitive information.

Contributor guide

Research direction
Investigate the snapshot mechanism used for unique key violation detection in PostgreSQL's bt check unique and compare with YugabyteDB's implementation in pgsql operation.cc to ensure consistency and improve pg compatibility.
Tech stack
ccpp
Domain
backenddatabase
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
PostgreSQL internalsC/C++Distributed systems
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20