> Changed to what? What is wrong in the way SUSPEND works now?

I thought that the article was clear enough.

A stored procedure call in Firebird is atomic.

What your procedure actually does is build an output set.

If the procedure completes without an exception, you get the
output set.

This is ok only when you work with small tables.

When you are dealing with big tables you need to be careful not to use stored procedures if you want decent response times.

A stored procedures that returns 500,000 will build a 500,000 output set in memory FIRST, THEN it will start returning the first row.

Very inefficient.

Rgds

Peppe