Foreign data wrappers concept in PostgreSQL - Time & Space Complexity

Time Complexity: Foreign data wrappers concept

O(n)

Understanding Time Complexity

When using foreign data wrappers, we access data stored outside our main database. Understanding time complexity helps us see how query time changes as the external data grows.

We want to know: How does the time to get data from a foreign source grow when that data gets bigger?

Scenario Under Consideration

Analyze the time complexity of this foreign table query.

CREATE EXTENSION IF NOT EXISTS postgres_fdw;
CREATE SERVER foreign_srv FOREIGN DATA WRAPPER postgres_fdw OPTIONS (host 'remote_host', dbname 'foreign_db');
CREATE USER MAPPING FOR CURRENT_USER SERVER foreign_srv OPTIONS (user 'foreign_user', password 'secret');

IMPORT FOREIGN SCHEMA public LIMIT TO (foreign_table) FROM SERVER foreign_srv INTO local_schema;

SELECT * FROM local_schema.foreign_table WHERE column = 'value';
    

This code sets up a connection to a remote database and queries a foreign table through the wrapper.

Identify Repeating Operations

Look at what repeats when querying foreign data.

• Primary operation: Fetching rows from the foreign table over the network.
• How many times: Once per row requested, depending on query and filters.

How Execution Grows With Input

As the foreign table grows, the number of rows to fetch can increase, making the query take longer.

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

Pattern observation: The time grows roughly in direct proportion to the number of rows fetched from the foreign source.

Final Time Complexity

Time Complexity: O(n)

This means the time to get data grows linearly with the number of rows fetched from the foreign table.

Common Mistake

[X] Wrong: "Querying a foreign table is always instant because it's just like a local table."

[OK] Correct: Accessing foreign data involves network calls and remote processing, so time grows with the amount of data fetched, unlike local tables.

Interview Connect

Understanding how foreign data wrappers affect query time shows you can think beyond local data and consider real-world data access costs. This skill helps you design efficient systems that work well with external data sources.

Self-Check

"What if we added a filter that reduces the number of rows fetched from the foreign table? How would the time complexity change?"

Practice

1. What is the main purpose of a Foreign Data Wrapper (FDW) in PostgreSQL?

easy

A. To speed up local query execution by caching results

B. To create backup copies of local tables automatically

C. To encrypt data stored in PostgreSQL tables

D. To access external data sources as if they were local tables

Solution

1. Step 1: Understand FDW functionality

   FDWs allow PostgreSQL to connect to external data sources and treat them like local tables.

2. Step 2: Compare options

   Options A, B, and D describe unrelated features: caching, backups, and encryption, not FDWs.

3. Final Answer:

   To access external data sources as if they were local tables -> Option D

4. Quick Check:

   FDW = Access external data like local tables [OK]

Hint: FDWs connect external data as local tables [OK]

Common Mistakes:

• Confusing FDW with backup or caching features
• Thinking FDW encrypts data
• Assuming FDW only works with local data

2. Which of the following is the correct SQL command to create a foreign server named myserver using the postgres_fdw wrapper?

easy

A. CREATE FOREIGN SERVER myserver FOREIGN DATA WRAPPER postgres_fdw;

B. CREATE SERVER myserver FOREIGN DATA WRAPPER postgres_fdw;

C. CREATE SERVER myserver USING FOREIGN DATA WRAPPER postgres_fdw;

D. CREATE FOREIGN SERVER myserver USING postgres_fdw;

Solution

1. Step 1: Recall correct syntax for creating foreign server

   The correct syntax is: CREATE FOREIGN SERVER server_name FOREIGN DATA WRAPPER wrapper_name;

2. Step 2: Match options to syntax

   CREATE FOREIGN SERVER myserver FOREIGN DATA WRAPPER postgres_fdw; matches exactly. Options A and C miss the FOREIGN keyword before SERVER. CREATE FOREIGN SERVER myserver USING postgres_fdw; uses USING incorrectly.

3. Final Answer:

   CREATE FOREIGN SERVER myserver FOREIGN DATA WRAPPER postgres_fdw; -> Option A

4. Quick Check:

   CREATE FOREIGN SERVER ... FOREIGN DATA WRAPPER ... [OK]

Hint: Use CREATE FOREIGN SERVER ... FOREIGN DATA WRAPPER ... [OK]

Common Mistakes:

• Omitting FOREIGN keyword before SERVER
• Using USING instead of FOREIGN DATA WRAPPER
• Mixing order of keywords

3. Given the following commands in PostgreSQL:

CREATE EXTENSION IF NOT EXISTS postgres_fdw;
CREATE SERVER foreign_srv FOREIGN DATA WRAPPER postgres_fdw OPTIONS (host '192.168.1.10', dbname 'remotedb');
CREATE USER MAPPING FOR current_user SERVER foreign_srv OPTIONS (user 'remoteuser', password 'remotepass');
CREATE FOREIGN TABLE foreign_table (id INT, name TEXT) SERVER foreign_srv OPTIONS (schema_name 'public', table_name 'users');
SELECT * FROM foreign_table WHERE id = 1;

What will the SELECT query do?

medium

A. Retrieve rows from the remote table users in remotedb where id = 1

B. Retrieve rows from the local table named foreign_table

C. Cause a syntax error because foreign_table is not a local table

D. Return an empty result because no data is copied locally

Solution

1. Step 1: Understand foreign table mapping

   The foreign table foreign_table maps to the remote table users in the remotedb database on host 192.168.1.10.

2. Step 2: Analyze the SELECT query

   The SELECT queries the foreign_table, which fetches data from the remote users table where id = 1.

3. Final Answer:

   Retrieve rows from the remote table users in remotedb where id = 1 -> Option A

4. Quick Check:

   Foreign table SELECT fetches remote data [OK]

Hint: Foreign tables query remote data transparently [OK]

Common Mistakes:

• Thinking foreign_table is local data
• Expecting syntax error on foreign table
• Assuming data is copied locally automatically

4. You run this command:

CREATE FOREIGN TABLE foreign_table (id INT, name TEXT) SERVER foreign_srv OPTIONS (schema_name 'public', table_name 'users');

But get an error: ERROR: foreign server "foreign_srv" does not exist
What is the most likely cause?

medium

A. The user mapping for foreign_srv is missing

B. The foreign table syntax is incorrect and missing parentheses

C. The foreign server foreign_srv was not created before creating the foreign table

D. The remote table users does not exist in the remote database

Solution

1. Step 1: Interpret the error message

   The error says foreign server "foreign_srv" does not exist, meaning PostgreSQL cannot find that server definition.

2. Step 2: Check prerequisites for foreign table creation

   Before creating a foreign table, the foreign server must be created. If missing, this error occurs.

3. Final Answer:

   The foreign server foreign_srv was not created before creating the foreign table -> Option C

4. Quick Check:

   Foreign server must exist before foreign table [OK]

Hint: Create foreign server before foreign table [OK]

Common Mistakes:

• Ignoring the need to create foreign server first
• Assuming user mapping causes this error
• Thinking syntax error causes this message

5. You want to combine data from a local table orders and a remote table customers accessed via FDW named cust_fdw. Which approach correctly joins these tables in PostgreSQL?

hard

A. Create a view combining orders and customers on the remote server

B. Create foreign table for customers via cust_fdw, then run: SELECT * FROM orders JOIN customers ON orders.customer_id = customers.id;

C. Use dblink to fetch customers data inside a subquery, then join with orders

D. Copy remote customers data into a local table, then join locally

Solution

1. Step 1: Understand FDW usage for joining local and remote data

   FDW allows creating a foreign table for remote customers, so you can join it directly with local orders.

2. Step 2: Evaluate options for combining data

   Create foreign table for customers via cust_fdw, then run: SELECT * FROM orders JOIN customers ON orders.customer_id = customers.id; uses FDW foreign table and a direct join, which is correct and efficient. Copy remote customers data into a local table, then join locally copies data manually, less dynamic. Use dblink to fetch customers data inside a subquery, then join with orders uses dblink, more complex. Create a view combining orders and customers on the remote server creates a view on remote server, not accessible locally.

3. Final Answer:

   Create foreign table for customers via cust_fdw, then run: SELECT * FROM orders JOIN customers ON orders.customer_id = customers.id; -> Option B

4. Quick Check:

   FDW foreign table join local table directly [OK]

Hint: Create foreign table, then join like local tables [OK]

Common Mistakes:

• Trying to join without creating foreign table
• Copying remote data manually instead of FDW
• Using dblink unnecessarily for simple joins