Search configuration and languages in PostgreSQL - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a text search configuration using the English dictionary.

PostgreSQL

CREATE TEXT SEARCH CONFIGURATION my_config ( COPY = [1] );

Drag options to blanks, or click blank then click option'

Aenglish

Bsimple

Cfrench

Dgerman

Attempts:

3 left

💡 Hint

Common Mistakes

Using a dictionary for a different language than intended.

Misspelling the dictionary name.

The english dictionary is used to create a text search configuration that supports English language processing.

2fill in blank

medium

Complete the code to add a mapping for the 'asciiword' token to use the 'english_stem' dictionary.

PostgreSQL

ALTER TEXT SEARCH CONFIGURATION my_config ALTER MAPPING FOR asciiword WITH [1];

Drag options to blanks, or click blank then click option'

Afrench_stem

Bsimple

Cenglish_stem

Dgerman_stem

Attempts:

3 left

💡 Hint

Common Mistakes

Using a dictionary for a different language.

Forgetting to specify the correct dictionary name.

The english_stem dictionary applies stemming rules for English words, improving search matching.

3fill in blank

hard

Fix the error in the code to set the default text search configuration to 'my_config'.

PostgreSQL

SET default_text_search_config = [1];

Drag options to blanks, or click blank then click option'

A'english'

B'simple'

Cmy_config

D'my_config'

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting quotes around the configuration name.

Using the wrong configuration name.

The configuration name must be a string literal, so it needs to be enclosed in single quotes.

4fill in blank

hard

Fill both blanks to create a text search dictionary using the 'snowball' template for the French language.

PostgreSQL

CREATE TEXT SEARCH DICTIONARY my_french_dict ( TEMPLATE = [1], Language = [2] );

Drag options to blanks, or click blank then click option'

A'snowball'

B'english'

C'french'

D'simple'

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing template and language values.

Using the wrong language name.

The snowball template supports stemming for multiple languages, and french specifies the language for the dictionary.

5fill in blank

hard

Fill all three blanks to create a text search configuration that copies from 'pg_catalog.english', alters the mapping for 'word' tokens to use 'my_french_dict', and sets it as default.

PostgreSQL

CREATE TEXT SEARCH CONFIGURATION my_french_config ( COPY = [1] );
ALTER TEXT SEARCH CONFIGURATION my_french_config ALTER MAPPING FOR word WITH [2];
SET default_text_search_config = [3];

Drag options to blanks, or click blank then click option'

Apg_catalog.english

Bmy_french_dict

C'my_french_config'

D'english'

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting quotes around string literals.

Using dictionary names with quotes in mapping.

Setting default config without quotes.

This sequence creates a configuration copying English settings, changes word token mapping to use the French dictionary, and sets the new configuration as default.

Practice

1. What is the main purpose of a search configuration in PostgreSQL?

easy

A. To define how text is processed for full-text search in a specific language

B. To store user login information securely

C. To manage database connections and pooling

D. To backup and restore database data

Solution

1. Step 1: Understand search configuration role

   Search configurations tell PostgreSQL how to handle text for searching, especially for different languages.

2. Step 2: Compare options

   Options A, C, and D relate to security, connections, and backups, not text processing.

3. Final Answer:

   To define how text is processed for full-text search in a specific language -> Option A

4. Quick Check:

   Search configuration = text processing [OK]

Hint: Search configs define text processing rules for languages [OK]

Common Mistakes:

• Confusing search configuration with user or connection settings
• Thinking it manages backups or security
• Assuming it stores data instead of processing text

2. Which of the following is the correct syntax to create a new text search configuration named my_config based on the built-in english configuration?

easy

A. CREATE TEXT SEARCH CONFIGURATION my_config AS english;

B. CREATE TEXT SEARCH CONFIGURATION my_config FROM english;

C. CREATE TEXT SEARCH CONFIGURATION my_config ( COPY = english );

D. CREATE TEXT SEARCH CONFIGURATION my_config LIKE english;

Solution

1. Step 1: Recall correct CREATE syntax

   PostgreSQL uses CREATE TEXT SEARCH CONFIGURATION name ( COPY = existing_config ) to copy an existing config.

2. Step 2: Check options

   Only CREATE TEXT SEARCH CONFIGURATION my_config ( COPY = english ); uses the correct syntax with COPY = english. Others use invalid keywords.

3. Final Answer:

   CREATE TEXT SEARCH CONFIGURATION my_config ( COPY = english ); -> Option C

4. Quick Check:

   Use COPY = for cloning configs [OK]

Hint: Use COPY = existing_config to clone search configs [OK]

Common Mistakes:

• Using FROM or AS instead of COPY =
• Omitting parentheses around COPY clause
• Confusing syntax with table creation

3. Given the following SQL commands:

CREATE TEXT SEARCH CONFIGURATION my_english ( COPY = english );
ALTER TEXT SEARCH CONFIGURATION my_english
  ALTER MAPPING FOR asciiword, asciihword, hword_asciipart
  WITH simple;
SELECT to_tsvector('my_english', 'PostgreSQL is great!');

What is the output of the SELECT statement?

medium

A. 'postgresql':1 'great':3 'is':2 'simple':5

B. 'postgresql':1 'great':3 'is':2

C. 'postgresql':1 'great':3

D. Syntax error due to ALTER MAPPING

Solution

1. Step 1: Understand ALTER MAPPING effect

   The ALTER MAPPING changes how asciiword and related tokens are processed, using the simple dictionary which does not remove stop words.

2. Step 2: Analyze to_tsvector output

   The text 'PostgreSQL is great!' produces tokens: 'PostgreSQL' (pos 1, asciiword) -> 'postgresql':1; 'is' (pos 2, asciiword) -> 'is':2; 'great' (pos 3, asciiword) -> 'great':3. Simple indexes all without dropping stopwords. Matches 'postgresql':1 'great':3 'is':2.

3. Final Answer:

   'postgresql':1 'great':3 'is':2 -> Option B

4. Quick Check:

   Alter mapping changes dictionary used [OK]

Hint: ALTER MAPPING changes dictionary for word processing [OK]

Common Mistakes:

• Assuming stop words are always removed
• Confusing dictionary effects on stemming and stop words
• Expecting syntax error from ALTER MAPPING

4. You run the following command:

ALTER TEXT SEARCH CONFIGURATION my_config
  ALTER MAPPING FOR word WITH english_stem;

But you get an error: ERROR: dictionary "english_stem" does not exist
What is the most likely cause?

medium

A. The configuration name is reserved and cannot be changed

B. ALTER MAPPING cannot be used on existing configurations

C. You must drop the configuration before altering it

D. The dictionary name is misspelled or not created

Solution

1. Step 1: Analyze error message

   The error says the dictionary "english_stem" does not exist, indicating PostgreSQL cannot find that dictionary.

2. Step 2: Identify cause

   Most likely, the dictionary name is misspelled or the dictionary was never created in the database.

3. Final Answer:

   The dictionary name is misspelled or not created -> Option D

4. Quick Check:

   Dictionary must exist before use [OK]

Hint: Check dictionary exists before ALTER MAPPING [OK]

Common Mistakes:

• Assuming ALTER MAPPING is disallowed on configs
• Trying to drop config unnecessarily
• Ignoring dictionary creation step

5. You want to create a search configuration for French that uses the built-in french configuration but replaces the stopword dictionary with a custom dictionary named my_french_stop. Which sequence of commands correctly achieves this?

hard

A. CREATE TEXT SEARCH CONFIGURATION my_french ( COPY = french );
ALTER TEXT SEARCH CONFIGURATION my_french
ALTER MAPPING FOR stopword WITH my_french_stop;

B. CREATE TEXT SEARCH CONFIGURATION my_french ( COPY = french );
ALTER TEXT SEARCH CONFIGURATION my_french
ALTER MAPPING FOR word WITH my_french_stop;

C. CREATE TEXT SEARCH CONFIGURATION my_french AS french;
ALTER TEXT SEARCH CONFIGURATION my_french
ALTER MAPPING FOR stopword WITH my_french_stop;

D. CREATE TEXT SEARCH CONFIGURATION my_french ( COPY = french );
ALTER TEXT SEARCH CONFIGURATION my_french
ALTER MAPPING FOR stopword WITH french;

Solution

1. Step 1: Create configuration by copying french

   Use CREATE TEXT SEARCH CONFIGURATION my_french ( COPY = french ); to clone the built-in french config.

2. Step 2: Alter mapping for stopword dictionary

   Use ALTER MAPPING FOR stopword WITH my_french_stop; to replace the stopword dictionary with the custom one.

3. Final Answer:

   CREATE TEXT SEARCH CONFIGURATION my_french ( COPY = french ); ALTER TEXT SEARCH CONFIGURATION my_french ALTER MAPPING FOR stopword WITH my_french_stop; -> Option A

4. Quick Check:

   Copy config then alter stopword mapping [OK]

Hint: Copy config then ALTER MAPPING for custom dictionaries [OK]

Common Mistakes:

• Using AS instead of COPY = for creation
• Altering wrong token types like word instead of stopword
• Assigning built-in dictionary instead of custom one