MySQL vs PostgreSQL vs SQLite - Performance Comparison

Time Complexity: MySQL vs PostgreSQL vs SQLite

O(n)

Understanding Time Complexity

When using different database systems like MySQL, PostgreSQL, and SQLite, it helps to understand how their operations grow as data grows.

We want to see how the time to run queries changes when the amount of data increases.

Scenario Under Consideration

Analyze the time complexity of a simple SELECT query on a table in each database.

SELECT * FROM users WHERE age > 30;
    

This query fetches all users older than 30 from a users table.

Identify Repeating Operations

Look at what repeats when the query runs.

• Primary operation: Scanning rows to check the age condition.
• How many times: Once for each row in the users table.

How Execution Grows With Input

As the number of users grows, the database checks more rows.

Input Size (n)	Approx. Operations
10	10 row checks
100	100 row checks
1000	1000 row checks

Pattern observation: The work grows directly with the number of rows.

Final Time Complexity

Time Complexity: O(n)

This means the time to run the query grows in a straight line as the table gets bigger.

Common Mistake

[X] Wrong: "All databases handle queries with the same speed no matter the data size."

[OK] Correct: Different databases use different methods like indexes that change how fast queries run as data grows.

Interview Connect

Understanding how query time grows helps you explain database choices and performance in real projects.

Self-Check

What if we add an index on the age column? How would the time complexity change?

Practice

1. Which database is best known for being lightweight and easy to set up without a server?

easy

A. SQLite

B. MySQL

C. PostgreSQL

D. Oracle

Solution

1. Step 1: Understand SQLite's design

   SQLite is designed as a serverless, self-contained database engine, making it lightweight and easy to use.

2. Step 2: Compare with other databases

   MySQL and PostgreSQL require server setup, unlike SQLite.

3. Final Answer:

   SQLite -> Option A

4. Quick Check:

   Lightweight and serverless = SQLite [OK]

Hint: Lightweight and no server means SQLite [OK]

Common Mistakes:

• Confusing MySQL as lightweight
• Thinking PostgreSQL is serverless
• Choosing Oracle which is not open-source

2. Which of the following is the correct way to start a MySQL server from the command line?

easy

A. service mysql start

B. mysql --start

C. start mysql

D. mysql start-server

Solution

1. Step 1: Recall MySQL server start commands

   On many systems, MySQL server is started using system service commands like 'service mysql start'.

2. Step 2: Check other options

   'mysql --start', 'start mysql', and 'mysql start-server' are not valid MySQL server start commands.

3. Final Answer:

   service mysql start -> Option A

4. Quick Check:

   Use system service command to start MySQL [OK]

Hint: Use 'service mysql start' to launch MySQL server [OK]

Common Mistakes:

• Using 'mysql --start' which is invalid
• Trying 'start mysql' which is not a command
• Confusing client commands with server commands

3. Given the following SQL snippet run on PostgreSQL, what will be the output?

SELECT version();

medium

A. An error because version() is not supported

B. Empty result set

C. The MySQL version string

D. The PostgreSQL version string

Solution

1. Step 1: Understand the version() function in PostgreSQL

   PostgreSQL supports the version() function which returns the current version string of the server.

2. Step 2: Evaluate the query output

   The query returns a single row with the PostgreSQL version details.

3. Final Answer:

   The PostgreSQL version string -> Option D

4. Quick Check:

   version() returns PostgreSQL version info [OK]

Hint: version() shows PostgreSQL version info [OK]

Common Mistakes:

• Assuming version() is MySQL-only
• Expecting an error from version()
• Thinking it returns empty result

4. You try to run this SQLite command but get an error:

CREATE DATABASE testdb;

What is the problem?

medium

A. Database name 'testdb' is reserved

B. Syntax error in the command

C. SQLite does not support CREATE DATABASE command

D. You need to specify a file path

Solution

1. Step 1: Understand SQLite database creation

   SQLite does not use CREATE DATABASE; it creates databases by opening a file.

2. Step 2: Analyze the error cause

   Using CREATE DATABASE causes an error because SQLite expects a file to open, not a database creation command.

3. Final Answer:

   SQLite does not support CREATE DATABASE command -> Option C

4. Quick Check:

   SQLite creates DB by file, no CREATE DATABASE [OK]

Hint: SQLite creates DB by file, no CREATE DATABASE command [OK]

Common Mistakes:

• Assuming CREATE DATABASE works in SQLite
• Thinking syntax is wrong
• Believing database names are reserved words

5. You want to choose a database for a web app that needs complex queries, full ACID compliance, and extensibility. Which is the best choice?

hard

A. SQLite

B. PostgreSQL

C. MySQL

D. MariaDB

Solution

1. Step 1: Identify requirements

   The app needs complex queries, full ACID compliance, and extensibility.

2. Step 2: Match database features

   PostgreSQL is known for advanced features, strong ACID compliance, and extensibility compared to SQLite and MySQL.

3. Final Answer:

   PostgreSQL -> Option B

4. Quick Check:

   Advanced features and ACID = PostgreSQL [OK]

Hint: Advanced features and ACID compliance point to PostgreSQL [OK]

Common Mistakes:

• Choosing SQLite for complex queries
• Picking MySQL over PostgreSQL for extensibility
• Confusing MariaDB as more advanced than PostgreSQL