Errata

PostgreSQL: Up and Running

Errata for PostgreSQL: Up and Running

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted by Date submitted
Chapter 1. The Basics; Why PostgreSQL; 8th paragraph

Grammatical error: Sentence should be:
"PostgreSQL just celebrated its 20th birthday, dating from its christening to PostgreSQL from Postgres95."
Note suggested use of possessive "its" rather than contraction "it's".

 Anonymous  Sep 13, 2017 
Chapter 1. The Basics; PostgreSQL Database Objects; Extension; 2nd paragraph

Spelling error: constituent

 Anonymous  Sep 13, 2017 
Chapter 1. The Basics; What's New in Latest Versions; ... 9.4; Using SQL to alter ...

Spelling error:
"... can now programmatically change system settings"
Note no 'd' on change.

 Anonymous  Sep 13, 2017 
ePub Page n/a
n/a

When loading the test data into the postgresql_book database, psql reports the following error:

106963: ERROR: multiple primary keys for table "test_scores" are not allowed

Lines 106962/3 referred to contains the statement:
ALTER TABLE ONLY test_scores
ADD CONSTRAINT pk_test_scores PRIMARY KEY (student, subject);

However, line 159 contains the statement:
CONSTRAINT pk_test_scores PRIMARY KEY (student, subject, test_date).

Presumably one of these needs to be deleted.

 Peter Silcock  Feb 13, 2019 
ePub Page 46
work_mem section last sentence

Changes require at leat a reload. Should read
Changes require at least a reload.

 Patrick Carlson  Aug 07, 2014 
PDF Page 52
Sample near bottom

\copy staging.factfinder_import FROM DEC_10_SF1_QTH1_with_ann.csv CSV

When I execute this code, I get 'schema "staging" does not exist'..and the code sample in the book occurs right after a paragraph discussing adding new schemas.

Note from the Author or Editor:
I'll check this out. We shuffled a lot of the content around so we may have moved this before the actual creation of the staging schema.

 Kurt  Feb 10, 2015 
Printed Page 88
1. Get the UTC ... and 2. Store the value 2012-02-15 04:08:00.

According to this website: http://www.timeanddate.com/worldclock/converter.html, the converted time should be 02:08:00 instead of the printed 04:08:00.

The examples below this part ar correct.

 Per-Otto Olsson  Mar 31, 2015