Bug 1276192

Summary:	Reduce transaction isolation level for profile_search table
Product:	[Community] Bugzilla	Reporter:	Matt Tyson 🤬 <mtyson>
Component:	Database	Assignee:	Matt Tyson 🤬 <mtyson>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.4	CC:	huiwang, jmcdonal, mtahir, qgong, vdanen
Target Milestone:	4.4
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.4.10044.10	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-16 00:42:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Matt Tyson 🤬 2015-10-29 03:08:11 UTC

The profile_search table stores recently used searches by the user.

When the user starts opening searches in quick succession, this can cause postgres serialization errors to happen.

These serialization errors really aren't all that critical for this table and could be safely ignored.

In Bugzilla/Search/Recent.pm we should wind the serialization level back to READ COMMITTED where it deletes from the profile_search table.

Comment 3 Rony Gong 🔥 2015-11-12 08:58:57 UTC

Test this on build 4.4.10042-7
Before upgrading, QE could get the serialization error when open huge amount tabs of search at once:
Red Hat Bugzilla's database reported a query serialization error. Most likely this occurred because another user or process attempted to change the same data that you were attempting to change. 

Please press Back and retry the transaction.

After upgrading, QE couldn't find the serialization error happened anymore.

Comment 4 Matt Tyson 🤬 2015-11-16 00:42:23 UTC

This change is now live. If there are any issues, do not reopen this bug.
Instead, you should create a new bug and reference this bug.