Converting PL/SQL to PL/pgSQL: Key Differences & Challenges Quiz

Home › PostgreSQL DBA › Converting PL/SQL to PL/pgSQL: Key Differences & Challenges

📝 Postgres Database Administration – Converting PL/SQL to PL/pgSQL: Key Differences & Challenges

20 questions · 15 min timer · Explanations included · Free

Which of the following is a common issue when converting PL/SQL triggers to PL/pgSQL?

PL/pgSQL does not support triggers.

PL/pgSQL triggers can only be row-level, not statement-level.

PL/pgSQL triggers must be written as functions.

PL/pgSQL triggers cannot access OLD and NEW values.

None

In PL/pgSQL, triggers must be implemented as functions, which is a different approach compared to PL/SQL.

What is a key difference in the way PL/SQL and PL/pgSQL handle sequence generation?

PL/pgSQL uses the NEXTVAL function for sequence generation, similar to PL/SQL.

PL/pgSQL does not support sequences.

PL/pgSQL requires sequences to be manually incremented.

PL/pgSQL sequences are automatically incremented without explicit calls.

None

PL/pgSQL uses the NEXTVAL function for sequence generation, similar to PL/SQL, maintaining consistency in this aspect.

Loading questions...

Click Submit to see your final score!

Time's up

Scroll to Top