-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Open
Labels
area/ysqlYugabyte SQL (YSQL)Yugabyte SQL (YSQL)kind/bugThis issue is a bugThis issue is a bugpriority/mediumMedium priority issueMedium priority issuestatus/awaiting-triageIssue awaiting triageIssue awaiting triage
Description
Jira Link: DB-19787
Description
Version - 2.29.0.0-b328
Steps-
- Create database, tables, partitions, indexes, constraints, materialized views and load data
- Create before row triggers on partition tables.
- Load some data using INSERTS and bulk copy from/to
- Create snapshot schedule and take time t1
- Detach existing partitions, attach new partitions
- Drop a few triggers, create new ones
- Restore to time t1 (PITR)
- Insert more data, create new triggers
- Do bunch of alters on the tables, including drop constraint, add column, rename columns, set default. The add constraint primary key fails intermittently around 20-30% of the times with error -
DatabaseError('deadlock detected\nDETAIL: Transaction 2d16d955-dfc8-4102-ad54-25a4a86dfdf6 aborted due to a deadlock: <1767962626864104>2d16d955-dfc8-4102-ad54-25a4a86dfdf6-><1767961902779172>a572b896-d6ea-4dee-b9b7-40a52af0b2c9->: kDeadlock\n')
ALTER query that fails - ALTER TABLE employees_hash ADD CONSTRAINT employees_hash_pkey PRIMARY KEY(id,age)
Issue reprod 2 times in about 10 runs and both times the same above query failed.
Issue Type
kind/bug
Warning: Please confirm that this issue does not contain any sensitive information
- I confirm this issue does not contain any sensitive information.
Metadata
Metadata
Assignees
Labels
area/ysqlYugabyte SQL (YSQL)Yugabyte SQL (YSQL)kind/bugThis issue is a bugThis issue is a bugpriority/mediumMedium priority issueMedium priority issuestatus/awaiting-triageIssue awaiting triageIssue awaiting triage