Strange variable behaviour when using it in limit clause in plpgsql stored procedure - Mailing list pgsql-general

From Sergey Moroz
Subject Strange variable behaviour when using it in limit clause in plpgsql stored procedure
Date
Msg-id 9d39d250711080350iafac9b0j31a059f11d6af88@mail.gmail.com
Whole thread Raw
Responses Re: Strange variable behaviour when using it in limit clause in plpgsql stored procedure  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
I tested performance of my query with limit clause inside plpgsql procedure. 2 slightly different situations:

1. Sql with limit clause and literal variable (for example 'select field1 from table1 limit 100')
2. The same sql with limit clause and pgplsql variable  (for example 'select field1 from table1 limit vilimit'). vilimit defined in declare section.

At first I compared execution plans. they were absolutely equal!
But in fact first procedure was 10 times!!!! faster then the second! What's the problem?!?!
Note: tested sql was complex enough. I didn't test this case on simple query like 'select field1 from table1 limit 100'.

--
Sincerely,
Sergey Moroz

pgsql-general by date:

Previous
From: "Albe Laurenz"
Date:
Subject: "Resurrected" data files - problem?
Next
From: "Peter Childs"
Date:
Subject: Re: "Resurrected" data files - problem?