High-Performance ACID Via Modular Concurrency Control

Total Page:16

File Type:pdf, Size:1020Kb

High-Performance ACID Via Modular Concurrency Control High-Performance ACID via Modular Concurrency Control Chao Xie1, Chunzhi Su1, Cody Littley1, Lorenzo Alvisi1, Manos Kapritsos2 and Yang Wang3 1The University of Texas at Austin 2Microsoft Research 3The Ohio State University Abstract: This paper describes the design, implementation, adopts the familiar abstraction offered by the ACID paradigm and evaluation of Callas, a distributed database system that and sets its sight on finding a more efficient way to implement offers to unmodified, transactional ACID applications the op- that abstraction. portunity to achieve a level of performance that can currently The key observation that motivates the architecture of only be reached by rewriting all or part of the application in a Callas is simple. While ease of programming requests that BASE/NoSQL style. The key to combining performance and ACID properties hold uniformly across all transactions, when ease of programming is to decouple the ACID abstraction— it comes to the mechanisms used to enforce these properties, which Callas offers identically for all transactions—from the uniformity can actually hinder performance: a concurrency mechanism used to support it. MCC, the new Modular ap- control mechanism that must work correctly for all possible proach to Concurrency Control at the core of Callas, makes pairs of transactions will necessarily have to make conserva- it possible to partition transactions in groups with the guar- tive assumptions, passing up opportunities for optimization. antee that, as long as the concurrency control mechanism Callas then decouples the concerns of abstraction and within each group upholds a given isolation property, that implementation: it offers ACID guarantees uniformly to all property will also hold among transactions in different groups. transactions, but uses a novel technique, modular concur- Because of their limited and specialized scope, these group- rency control (MCC), to customize the mechanism through specific mechanisms can be customized for concurrency with which these guarantees are provided. unprecedented aggressiveness. In our MySQL Cluster-based MCC makes it possible to think modularly about the en- prototype, Callas yields an 8.2x throughput gain for TPC-C forcement of any given isolation property I. It enables Callas with no programming effort. to partition transactions in separate groups, and it ensures that as long as I holds within each group, it will also hold among transactions in different groups. Separating concerns 1 Introduction frees Callas to use within each group concurrency control mechanisms optimized for that group’s transactions. Thus, This paper describes the design, implementation, and eval- Callas can find opportunities for increased concurrency where uation of Callas, a distributed database system that aims to a generic mechanism might have to settle for a conservative unlock the performance potential of the ACID transactional execution. paradigm, without sacrificing its generality and simplicity. To maximize the impact of MCC on scalability, Callas Performance is not traditionally one of ACID’s strong heuristically focuses on identifying the best grouping for suits: after all, the BASE/NoSQL movement [10, 17, 23, 26] those transactions whose high conflict rate bottlenecks the was born out of frustration with the limited scalability of application and can therefore most benefit from an aggres- traditional ACID solutions, only to become itself a source of sive concurrency control mechanism, leaving the rest in a frustration once the challenges of programming applications single, large group. Such performance-critical transactions in this new paradigm began to sink in. are typically few [33], which results in two advantages for Callas aims to move beyond the ACID/BASE dilemma. Callas. Rather than trying to draw performance from weakening the First, it permits the systematic study of the performance abstraction offered to the programmer, Callas unequivocally benefits of grouping—though we find that even a simple greedy heuristic can yield substantial returns. Second, it enables concurrency control mechanisms that, Permission to make digital or hard copies of all or part of this work for personal or because of their limited and specialized scope, can seek oppor- classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation tunities for concurrency with unprecedented aggressiveness. on the first page. Copyrights for components of this work owned by others than ACM For example, Callas’ in-group mechanism uses two novel run- must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a time techniques that, by refining the static analysis approach fee. Request permissions from [email protected]. used by transaction chopping [29], create new chances for SOSP’15, October 4–7, 2015, Monterey, CA. Copyright c 2015 ACM 978-1-4503-3834-9/15/10. $15.00. concurrency. http://dx.doi.org/10.1145/2815400.2815430 Even existing mechanisms designed to boost concurrency, however, can benefit from a more limited scope. In particular, // transfer balance // sum balance (infrequent) begin transaction we find that also traditional transaction chopping, which re- begin transaction bal dest = bal dest + val return bal orig + bal dest bal orig = bal orig − val lies on the absence of certain dependency cycles among all commit transactions, becomes much more incisive when the lack of commit circular dependency must apply only to the small number of Fig. 1: A simple banking application. transactions within a group. In summary, we make the following contributions: plicity, when it comes to enforcing isolation this choice can • We propose MCC, a new, modular approach to concur- become an obstacle to performance and scalability. Whether rency control. By decoupling abstraction from mechanism, using locking or optimistic concurrency control (OCC), cur- MCC retains the simplicity of a uniform ACID API; by rent ACID databases rely on one-size-fits-all—and thus fun- separating concerns, it lets each module customize its in- damentally conservative—mechanisms to ensure isolation. ternal concurrency control mechanism to achieve greater For example, when a transaction accesses an object (e.g., concurrency without sacrificing safety. a database row), a lock-based mechanism must acquire a • We introduce Runtime Pipelining, a technique that lever- lock that is held until the end of the transaction, preventing ages execution-time information to aggressively weaken all other transactions from observing intermediate states of within a group the conservative requirements of the current that transaction. Perhaps surprisingly, given their name, OCC theory of safe transaction chopping [29] and gain, as a re- mechanisms are, in their own way, equally conservative. Al- sult, unprecedented opportunities for concurrency. The key though they allow transactions to speculatively execute in to the effectiveness of Runtime Pipelining is the flexibility parallel without acquiring locks, they do not refine the crite- offered by MCC, which makes this technique applicable ria for determining contention, but simply delay the check: if within small groups of well-suited transactions. contention is detected at commit time, they force all but one of the contending transactions to rollback. • We present the design, implementation and evaluation of By treating all transactions equally, one-size-fits-all mech- Callas, a prototype implementation of MCC within a mod- anisms cannot take advantage of workload-specific optimiza- ified MySQL Cluster distributed database. Our evaluation tions. Isolation is uniformly enforced to prevent all other of Callas suggests that MCC can deliver significant per- transactions from observing intermediate states. In some cir- formance gains to unmodified ACID applications. For ex- cumstances, however, such precautions are excessive: it is ample, we find that, for TPC-C, Callas achieves an 8.2x quite common to find transactions that can safely expose speedup over MySQL Cluster without requiring any pro- some of their intermediate states to some other transactions. gramming effort. Consider, for example, how a lock-based mechanism The rest of the paper is organized as follows. After Sec- would handle the simple banking application that uses the two tion 2 discusses why an undifferentiated concurrency control transactions defined in Figure 1: transfer balance deducts mechanism is undesirable, Section 3 introduces MCC and some amount from the bal orig account and adds it to specifies the correctness conditions that any valid instanti- bal dest; sum balance computes the total assets across the ation of MCC must meet. Section 4 and Section 5 present two accounts. the mechanisms Callas uses to ensure isolation across groups When these transactions can execute concurrently, uni- and within each group, respectively. The implementation of formly enforcing isolation requires transfer balance to keep Callas is the topic of Section 6, while Section 7 presents the the lock on bal dest until the transaction commits, to prevent results of our experimental evaluation. Section 8 discusses sum balance from computing the wrong total by observing related work, and Section 9 concludes the paper. the intermediate state where bal dest has been credited but bal orig not yet charged. Keeping the locks for so long, how-
Recommended publications
  • Not ACID, Not BASE, but SALT a Transaction Processing Perspective on Blockchains
    Not ACID, not BASE, but SALT A Transaction Processing Perspective on Blockchains Stefan Tai, Jacob Eberhardt and Markus Klems Information Systems Engineering, Technische Universitat¨ Berlin fst, je, [email protected] Keywords: SALT, blockchain, decentralized, ACID, BASE, transaction processing Abstract: Traditional ACID transactions, typically supported by relational database management systems, emphasize database consistency. BASE provides a model that trades some consistency for availability, and is typically favored by cloud systems and NoSQL data stores. With the increasing popularity of blockchain technology, another alternative to both ACID and BASE is introduced: SALT. In this keynote paper, we present SALT as a model to explain blockchains and their use in application architecture. We take both, a transaction and a transaction processing systems perspective on the SALT model. From a transactions perspective, SALT is about Sequential, Agreed-on, Ledgered, and Tamper-resistant transaction processing. From a systems perspec- tive, SALT is about decentralized transaction processing systems being Symmetric, Admin-free, Ledgered and Time-consensual. We discuss the importance of these dual perspectives, both, when comparing SALT with ACID and BASE, and when engineering blockchain-based applications. We expect the next-generation of decentralized transactional applications to leverage combinations of all three transaction models. 1 INTRODUCTION against. Using the admittedly contrived acronym of SALT, we characterize blockchain-based transactions There is a common belief that blockchains have the – from a transactions perspective – as Sequential, potential to fundamentally disrupt entire industries. Agreed, Ledgered, and Tamper-resistant, and – from Whether we are talking about financial services, the a systems perspective – as Symmetric, Admin-free, sharing economy, the Internet of Things, or future en- Ledgered, and Time-consensual.
    [Show full text]
  • Failures in DBMS
    Chapter 11 Database Recovery 1 Failures in DBMS Two common kinds of failures StSystem filfailure (t)(e.g. power outage) ‒ affects all transactions currently in progress but does not physically damage the data (soft crash) Media failures (e.g. Head crash on the disk) ‒ damagg()e to the database (hard crash) ‒ need backup data Recoveryyp scheme responsible for handling failures and restoring database to consistent state 2 Recovery Recovering the database itself Recovery algorithm has two parts ‒ Actions taken during normal operation to ensure system can recover from failure (e.g., backup, log file) ‒ Actions taken after a failure to restore database to consistent state We will discuss (briefly) ‒ Transactions/Transaction recovery ‒ System Recovery 3 Transactions A database is updated by processing transactions that result in changes to one or more records. A user’s program may carry out many operations on the data retrieved from the database, but the DBMS is only concerned with data read/written from/to the database. The DBMS’s abstract view of a user program is a sequence of transactions (reads and writes). To understand database recovery, we must first understand the concept of transaction integrity. 4 Transactions A transaction is considered a logical unit of work ‒ START Statement: BEGIN TRANSACTION ‒ END Statement: COMMIT ‒ Execution errors: ROLLBACK Assume we want to transfer $100 from one bank (A) account to another (B): UPDATE Account_A SET Balance= Balance -100; UPDATE Account_B SET Balance= Balance +100; We want these two operations to appear as a single atomic action 5 Transactions We want these two operations to appear as a single atomic action ‒ To avoid inconsistent states of the database in-between the two updates ‒ And obviously we cannot allow the first UPDATE to be executed and the second not or vice versa.
    [Show full text]
  • SQL Vs Nosql: a Performance Comparison
    SQL vs NoSQL: A Performance Comparison Ruihan Wang Zongyan Yang University of Rochester University of Rochester [email protected] [email protected] Abstract 2. ACID Properties and CAP Theorem We always hear some statements like ‘SQL is outdated’, 2.1. ACID Properties ‘This is the world of NoSQL’, ‘SQL is still used a lot by We need to refer the ACID properties[12]: most of companies.’ Which one is accurate? Has NoSQL completely replace SQL? Or is NoSQL just a hype? SQL Atomicity (Structured Query Language) is a standard query language A transaction is an atomic unit of processing; it should for relational database management system. The most popu- either be performed in its entirety or not performed at lar types of RDBMS(Relational Database Management Sys- all. tems) like Oracle, MySQL, SQL Server, uses SQL as their Consistency preservation standard database query language.[3] NoSQL means Not A transaction should be consistency preserving, meaning Only SQL, which is a collection of non-relational data stor- that if it is completely executed from beginning to end age systems. The important character of NoSQL is that it re- without interference from other transactions, it should laxes one or more of the ACID properties for a better perfor- take the database from one consistent state to another. mance in desired fields. Some of the NOSQL databases most Isolation companies using are Cassandra, CouchDB, Hadoop Hbase, A transaction should appear as though it is being exe- MongoDB. In this paper, we’ll outline the general differences cuted in iso- lation from other transactions, even though between the SQL and NoSQL, discuss if Relational Database many transactions are execut- ing concurrently.
    [Show full text]
  • APPENDIX G Acid Dissociation Constants
    harxxxxx_App-G.qxd 3/8/10 1:34 PM Page AP11 APPENDIX G Acid Dissociation Constants §␮ ϭ 0.1 M 0 ؍ (Ionic strength (␮ † ‡ † Name Structure* pKa Ka pKa ϫ Ϫ5 Acetic acid CH3CO2H 4.756 1.75 10 4.56 (ethanoic acid) N ϩ H3 ϫ Ϫ3 Alanine CHCH3 2.344 (CO2H) 4.53 10 2.33 ϫ Ϫ10 9.868 (NH3) 1.36 10 9.71 CO2H ϩ Ϫ5 Aminobenzene NH3 4.601 2.51 ϫ 10 4.64 (aniline) ϪO SNϩ Ϫ4 4-Aminobenzenesulfonic acid 3 H3 3.232 5.86 ϫ 10 3.01 (sulfanilic acid) ϩ NH3 ϫ Ϫ3 2-Aminobenzoic acid 2.08 (CO2H) 8.3 10 2.01 ϫ Ϫ5 (anthranilic acid) 4.96 (NH3) 1.10 10 4.78 CO2H ϩ 2-Aminoethanethiol HSCH2CH2NH3 —— 8.21 (SH) (2-mercaptoethylamine) —— 10.73 (NH3) ϩ ϫ Ϫ10 2-Aminoethanol HOCH2CH2NH3 9.498 3.18 10 9.52 (ethanolamine) O H ϫ Ϫ5 4.70 (NH3) (20°) 2.0 10 4.74 2-Aminophenol Ϫ 9.97 (OH) (20°) 1.05 ϫ 10 10 9.87 ϩ NH3 ϩ ϫ Ϫ10 Ammonia NH4 9.245 5.69 10 9.26 N ϩ H3 N ϩ H2 ϫ Ϫ2 1.823 (CO2H) 1.50 10 2.03 CHCH CH CH NHC ϫ Ϫ9 Arginine 2 2 2 8.991 (NH3) 1.02 10 9.00 NH —— (NH2) —— (12.1) CO2H 2 O Ϫ 2.24 5.8 ϫ 10 3 2.15 Ϫ Arsenic acid HO As OH 6.96 1.10 ϫ 10 7 6.65 Ϫ (hydrogen arsenate) (11.50) 3.2 ϫ 10 12 (11.18) OH ϫ Ϫ10 Arsenious acid As(OH)3 9.29 5.1 10 9.14 (hydrogen arsenite) N ϩ O H3 Asparagine CHCH2CNH2 —— —— 2.16 (CO2H) —— —— 8.73 (NH3) CO2H *Each acid is written in its protonated form.
    [Show full text]
  • Drugs and Acid Dissociation Constants Ionisation of Drug Molecules Most Drugs Ionise in Aqueous Solution.1 They Are Weak Acids Or Weak Bases
    Drugs and acid dissociation constants Ionisation of drug molecules Most drugs ionise in aqueous solution.1 They are weak acids or weak bases. Those that are weak acids ionise in water to give acidic solutions while those that are weak bases ionise to give basic solutions. Drug molecules that are weak acids Drug molecules that are weak bases where, HA = acid (the drug molecule) where, B = base (the drug molecule) H2O = base H2O = acid A− = conjugate base (the drug anion) OH− = conjugate base (the drug anion) + + H3O = conjugate acid BH = conjugate acid Acid dissociation constant, Ka For a drug molecule that is a weak acid The equilibrium constant for this ionisation is given by the equation + − where [H3O ], [A ], [HA] and [H2O] are the concentrations at equilibrium. In a dilute solution the concentration of water is to all intents and purposes constant. So the equation is simplified to: where Ka is the acid dissociation constant for the weak acid + + Also, H3O is often written simply as H and the equation for Ka is usually written as: Values for Ka are extremely small and, therefore, pKa values are given (similar to the reason pH is used rather than [H+]. The relationship between pKa and pH is given by the Henderson–Hasselbalch equation: or This relationship is important when determining pKa values from pH measurements. Base dissociation constant, Kb For a drug molecule that is a weak base: 1 Ionisation of drug molecules. 1 Following the same logic as for deriving Ka, base dissociation constant, Kb, is given by: and Ionisation of water Water ionises very slightly.
    [Show full text]
  • Concurrency Control
    Concurrency Control Instructor: Matei Zaharia cs245.stanford.edu Outline What makes a schedule serializable? Conflict serializability Precedence graphs Enforcing serializability via 2-phase locking » Shared and exclusive locks » Lock tables and multi-level locking Optimistic concurrency with validation Concurrency control + recovery CS 245 2 Lock Modes Beyond S/X Examples: (1) increment lock (2) update lock CS 245 3 Example 1: Increment Lock Atomic addition action: INi(A) {Read(A); A ¬ A+k; Write(A)} INi(A), INj(A) do not conflict, because addition is commutative! CS 245 4 Compatibility Matrix compat S X I S T F F X F F F I F F T CS 245 5 Update Locks A common deadlock problem with upgrades: T1 T2 l-S1(A) l-S2(A) l-X1(A) l-X2(A) --- Deadlock --- CS 245 6 Solution If Ti wants to read A and knows it may later want to write A, it requests an update lock (not shared lock) CS 245 7 Compatibility Matrix New request compat S X U S T F Lock already X F F held in U CS 245 8 Compatibility Matrix New request compat S X U S T F T Lock already X F F F held in U F F F Note: asymmetric table! CS 245 9 How Is Locking Implemented In Practice? Every system is different (e.g., may not even provide conflict serializable schedules) But here is one (simplified) way ... CS 245 10 Sample Locking System 1. Don’t ask transactions to request/release locks: just get the weakest lock for each action they perform 2.
    [Show full text]
  • Sundial: Harmonizing Concurrency Control and Caching in a Distributed OLTP Database Management System
    Sundial: Harmonizing Concurrency Control and Caching in a Distributed OLTP Database Management System Xiangyao Yu, Yu Xia, Andrew Pavlo♠ Daniel Sanchez, Larry Rudolph|, Srinivas Devadas Massachusetts Institute of Technology, ♠Carnegie Mellon University, |Two Sigma Investments, LP [email protected], [email protected], [email protected] [email protected], [email protected], [email protected] ABSTRACT and foremost, long network delays lead to long execution time of Distributed transactions suffer from poor performance due to two distributed transactions, making them slower than single-partition major limiting factors. First, distributed transactions suffer from transactions. Second, long execution time increases the likelihood high latency because each of their accesses to remote data incurs a of contention among transactions, leading to more aborts and per- long network delay. Second, this high latency increases the likeli- formance degradation. hood of contention among distributed transactions, leading to high Recent work on improving distributed concurrency control has abort rates and low performance. focused on protocol-level and hardware-level improvements. Im- We present Sundial, an in-memory distributed optimistic concur- proved protocols can reduce synchronization overhead among trans- rency control protocol that addresses these two limitations. First, to actions [22, 35, 36, 46], but can still limit performance due to high reduce the transaction abort rate, Sundial dynamically determines coordination overhead (e.g., lock blocking). Hardware-level im- the logical order among transactions at runtime, based on their data provements include using special hardware like optimized networks access patterns. Sundial achieves this by applying logical leases to that enable low-latency remote memory accesses [20, 48, 55], which each data element, which allows the database to dynamically calcu- can increase the overall cost of the system.
    [Show full text]
  • Implementing Distributed Transactions Distributed Transaction Distributed Database Systems ACID Properties Global Atomicity Atom
    Distributed Transaction • A distributed transaction accesses resource managers distributed across a network Implementing Distributed • When resource managers are DBMSs we refer to the Transactions system as a distributed database system Chapter 24 DBMS at Site 1 Application Program DBMS 1 at Site 2 2 Distributed Database Systems ACID Properties • Each local DBMS might export • Each local DBMS – stored procedures, or – supports ACID properties locally for each subtransaction – an SQL interface. • Just like any other transaction that executes there • In either case, operations at each site are grouped – eliminates local deadlocks together as a subtransaction and the site is referred • The additional issues are: to as a cohort of the distributed transaction – Global atomicity: all cohorts must abort or all commit – Each subtransaction is treated as a transaction at its site – Global deadlocks: there must be no deadlocks involving • Coordinator module (part of TP monitor) supports multiple sites ACID properties of distributed transaction – Global serialization: distributed transaction must be globally serializable – Transaction manager acts as coordinator 3 4 Atomic Commit Protocol Global Atomicity Transaction (3) xa_reg • All subtransactions of a distributed transaction Manager Resource must commit or all must abort (coordinator) Manager (1) tx_begin (cohort) • An atomic commit protocol, initiated by a (4) tx_commit (5) atomic coordinator (e.g., the transaction manager), commit protocol ensures this. (3) xa_reg Resource Application – Coordinator
    [Show full text]
  • Concurrency Control and Recovery ACID • Transactions • Recovery Transaction Model Concurency Control Recovery
    Data Management Systems • Transaction Processing • Concurrency control and recovery ACID • Transactions • Recovery Transaction model Concurency Control Recovery Gustavo Alonso Institute of Computing Platforms Department of Computer Science ETH Zürich Transactions-CC&R 1 A bit of theory • Before discussing implementations, we will cover the theoretical underpinning behind concurrency control and recovery • Discussion at an abstract level, without relation to implementations • No consideration of how the concepts map to real elements (tuples, pages, blocks, buffers, etc.) • Theoretical background important to understand variations in implementations and what is considered to be correct • Theoretical background also key to understand how system have evolved over the years Transactions-CC&R 2 Reference Concurrency Control and Recovery in Database Systems Philip A. Bernstein, Vassos Hadzilacos, Nathan Goodman • https://www.microsoft.com/en- us/research/people/philbe/book/ Transactions-CC&R 3 ACID Transactions-CC&R 4 Conventional notion of database correctness • ACID: • Atomicity: the notion that an operation or a group of operations must take place in their entirety or not at all • Consistency: operations should take the database from a correct state to another correct state • Isolation: concurrent execution of operations should yield results that are predictable and correct • Durability: the database needs to remember the state it is in at all moments, even when failures occur • Like all acronyms, more effort in making it sound cute than in
    [Show full text]
  • CAS CS 460/660 Introduction to Database Systems Transactions
    CAS CS 460/660 Introduction to Database Systems Transactions and Concurrency Control 1.1 Recall: Structure of a DBMS Query in: e.g. “Select min(account balance)” Data out: Database app e.g. 2000 Query Optimization and Execution Relational Operators These layers Access Methods must consider concurrency Buffer Management control and recovery Disk Space Management Customer accounts stored on disk1.2 = File System vs. DBMS? ■ Thought Experiment 1: ➹ You and your project partner are editing the same file. ➹ You both save it at the same time. ➹ Whose changes survive? A) Yours B) Partner’s C) Both D) Neither E) ??? • Thought Experiment 2: Q: How do you write programs over a – You’re updating a file. subsystem when it – The power goes out. promises you only “???” ? – Which of your changes survive? A: Very, very carefully!! A) All B) None C) All Since last save D ) ??? 1.3 Concurrent Execution ■ Concurrent execution essential for good performance. ➹ Because disk accesses are frequent, and relatively slow, it is important to keep the CPU humming by working on several user programs concurrently. ➹ Trends are towards lots of cores and lots of disks. § e.g., IBM Watson has 2880 processing cores ■ A program may carry out many operations, but the DBMS is only concerned about what data is read/written from/to the database. 1.4 Key concept: Transaction ■ an atomic sequence of database actions (reads/writes) ■ takes DB from one consistent state to another ■ transaction - DBMS’s abstract view of a user program: ➹ a sequence of reads and writes. transaction
    [Show full text]
  • Write-Ahead Logging (WAL) Protocol
    CSC 261/461 – Database Systems Lecture 23 Fall 2017 CSC 261, Fall 2017, UR Announcements • Project 3 Due on: 12/01 • Poster: – Will be viewed by the whole department – Even, you may present it later – So, make sure, there is no typo and no embarrassing error. – Go through the poster multiple times – Strongly recommended: • Send us a copy by Sunday. We will try to give you quick feedback. • You can send the poster for printing on Tuesday CSC 261, Fall 2017, UR Today’s Lecture 1. Transactions 2. Properties of Transactions: ACID 3. Logging CSC 261, Fall 2017, UR TRANSACTIONS CSC 261, Fall 2017, UR Transactions: Basic Definition A transaction (“TXN”) is a sequence In the real world, a TXN of one or more operations (reads or either happened writes) which reflects a single real- completely or not at all world transition. START TRANSACTION UPDATE Product SET Price = Price – 1.99 WHERE pname = ‘Gizmo’ COMMIT CSC 261, Fall 2017, UR Transactions: Basic Definition A transaction (“TXN”) is a sequence of one or In the real world, a TXN more operations (reads or writes) which either happened reflects a single real-world transition. completely or not at all Examples: • Transfer money between accounts • Purchase a group of products • Register for a class (either waitlist or allocated) CSC 261, Fall 2017, UR Transactions in SQL • In “ad-hoc” SQL: – Default: each statement = one transaction • In a program, multiple statements can be grouped together as a transaction: START TRANSACTION UPDATE Bank SET amount = amount – 100 WHERE name = ‘Bob’ UPDATE Bank SET amount = amount + 100 WHERE name = ‘Joe’ COMMIT CSC 261, Fall 2017, UR Motivation for Transactions Grouping user actions (reads & writes) into transactions helps with two goals: 1.
    [Show full text]
  • Phosphoric Acid
    Common Name: PHOSPHORIC ACID CAS Number: 7664-38-2 RTK Substance number: 1516 DOT Number: UN 1805 Date: May 1997 Revision: April 2004 --------------------------------------------------------------------------- --------------------------------------------------------------------------- HAZARD SUMMARY WORKPLACE EXPOSURE LIMITS * Phosphoric Acid can affect you when breathed in. OSHA: The legal airborne permissible exposure limit * Phosphoric Acid is a CORROSIVE CHEMICAL and (PEL) is 1 mg/m3 averaged over an 8-hour contact can irritate and burn the eyes. workshift. * Breathing Phosphoric Acid can irritate the nose, throat and lungs causing coughing and wheezing. NIOSH: The recommended airborne exposure limit is * Long-term exposure to the liquid may cause drying and 1 mg/m3 averaged over a 10-hour workshift and cracking of the skin. 3 mg/m3, not to be exceeded during any 15 minute work period. IDENTIFICATION Phosphoric Acid is a colorless, odorless solid or a thick, clear ACGIH: The recommended airborne exposure limit is 1 mg/m3 averaged over an 8-hour workshift and liquid. It is used in rustproofing metals, fertilizers, detergents, 3 foods, beverages, and water treatment. 3 mg/m as a STEL (short term exposure limit). REASON FOR CITATION WAYS OF REDUCING EXPOSURE * Phosphoric Acid is on the Hazardous Substance List * Where possible, enclose operations and use local exhaust because it is regulated by OSHA and cited by ACGIH, ventilation at the site of chemical release. If local exhaust DOT, NIOSH, IRIS, NFPA and EPA. ventilation or enclosure is not used, respirators should be * This chemical is on the Special Health Hazard Substance worn. List because it is CORROSIVE. * Wear protective work clothing. * Definitions are provided on page 5.
    [Show full text]