list clearer. 5.2. What to Report The most important thing to remember about bug reporting is to state all the facts and only facts. Do not speculate what you think went wrong, what “it seemed to do”, output, this would be a good time to start doing so. • The output you expected is very important to state. If you just write “This command gives me that output.” or “This is not what I expected.”, we might SET temp_hi = temp_hi - 2, temp_lo = temp_lo - 2 WHERE date > '1994-11-28'; Look at the new state of the data: SELECT * FROM weather; 14 The SQL Language city | temp_lo | temp_hi | prcp

xxxiii Preface 5.2. What to Report The most important thing to remember about bug reporting is to state all the facts and only facts. Do not speculate what you think went wrong, what “it seemed to do”, output, this would be a good time to start doing so. • The output you expected is very important to state. If you just write “This command gives me that output.” or “This is not what I expected.”, we might SET temp_hi = temp_hi - 2, temp_lo = temp_lo - 2 WHERE date > '1994-11-28'; Look at the new state of the data: SELECT * FROM weather; city | temp_lo | temp_hi | prcp | date -------

list clearer. 5.2. What to Report The most important thing to remember about bug reporting is to state all the facts and only facts. Do not speculate what you think went wrong, what “it seemed to do”, output, this would be a good time to start doing so. • The output you expected is very important to state. If you just write “This command gives me that output.” or “This is not what I expected.”, we might SET temp_hi = temp_hi - 2, temp_lo = temp_lo - 2 WHERE date > '1994-11-28'; Look at the new state of the data: SELECT * FROM weather; city | temp_lo | temp_hi | prcp | date -------

xxxv Preface 5.2. What to Report The most important thing to remember about bug reporting is to state all the facts and only facts. Do not speculate what you think went wrong, what “it seemed to do”, output, this would be a good time to start doing so. • The output you expected is very important to state. If you just write “This command gives me that output.” or “This is not what I expected.”, we might SET temp_hi = temp_hi - 2, temp_lo = temp_lo - 2 WHERE date > '1994-11-28'; Look at the new state of the data: SELECT * FROM weather; city | temp_lo | temp_hi | prcp | date -------

list clearer. 5.2. What to Report The most important thing to remember about bug reporting is to state all the facts and only facts. Do not speculate what you think went wrong, what “it seemed to do”, output, this would be a good time to start doing so. • The output you expected is very important to state. If you just write “This command gives me that output.” or “This is not what I expected.”, we might - 2, temp_lo = temp_lo - 2 WHERE date > '1994-11-28'; 16 The SQL Language Look at the new state of the data: SELECT * FROM weather; city | temp_lo | temp_hi | prcp | date -------

list clearer. 5.2. What to Report The most important thing to remember about bug reporting is to state all the facts and only facts. Do not speculate what you think went wrong, what “it seemed to do”, output, this would be a good time to start doing so. • The output you expected is very important to state. If you just write “This command gives me that output.” or “This is not what I expected.”, we might SET temp_hi = temp_hi - 2, temp_lo = temp_lo - 2 WHERE date > '1994-11-28'; Look at the new state of the data: SELECT * FROM weather; city | temp_lo | temp_hi | prcp | date -------

xxxv Preface 5.2. What to Report The most important thing to remember about bug reporting is to state all the facts and only facts. Do not speculate what you think went wrong, what “it seemed to do”, output, this would be a good time to start doing so. • The output you expected is very important to state. If you just write “This command gives me that output.” or “This is not what I expected.”, we might SET temp_hi = temp_hi - 2, temp_lo = temp_lo - 2 WHERE date > '1994-11-28'; Look at the new state of the data: SELECT * FROM weather; city | temp_lo | temp_hi | prcp | date -------

xxxiv Preface 5.2. What to Report The most important thing to remember about bug reporting is to state all the facts and only facts. Do not speculate what you think went wrong, what “it seemed to do”, output, this would be a good time to start doing so. • The output you expected is very important to state. If you just write “This command gives me that output.” or “This is not what I expected.”, we might SET temp_hi = temp_hi - 2, temp_lo = temp_lo - 2 WHERE date > '1994-11-28'; Look at the new state of the data: SELECT * FROM weather; city | temp_lo | temp_hi | prcp | date -------

xxxv Preface 5.2. What to Report The most important thing to remember about bug reporting is to state all the facts and only facts. Do not speculate what you think went wrong, what “it seemed to do”, output, this would be a good time to start doing so. • The output you expected is very important to state. If you just write “This command gives me that output.” or “This is not what I expected.”, we might SET temp_hi = temp_hi - 2, temp_lo = temp_lo - 2 WHERE date > '1994-11-28'; Look at the new state of the data: SELECT * FROM weather; city | temp_lo | temp_hi | prcp | date -------

.................................... 2806 F.25. pg_buffercache — inspect PostgreSQL buffer cache state ........................ 2807 F.26. pgcrypto — cryptographic functions .......................... xxxv Preface 5.2. What to Report The most important thing to remember about bug reporting is to state all the facts and only facts. Do not speculate what you think went wrong, what “it seemed to do”, output, this would be a good time to start doing so. • The output you expected is very important to state. If you just write “This command gives me that output.” or “This is not what I expected.”, we might