| From: | Ravi Krishna <ravikrishna(at)mail(dot)com> |
|---|---|
| To: | viru_7683(at)yahoo(dot)com |
| Cc: | Pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Prepare Statement VS Literal Values |
| Date: | 2021-04-11 23:44:56 |
| Message-ID: | trinity-d350f837-60e7-4fc1-a5e4-51c22ba53ccf-1618184696073@3c-app-mailcom-lxa16 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>This looks like early vs late binding problem, also seen in other products. When you prepare the sql, the optimizer<br/>
has no way of knowing the values which is going to be supplied in future. So it is possible that at the time of preparing<br/>
PG settles on a plan and uses it for all values, regardless of its efficiency.</div>
<div> </div></div></body></html>
| Attachment | Content-Type | Size |
|---|---|---|
| unknown_filename | text/html | 476 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Igor Korot | 2021-04-11 23:49:11 | Re: How can I insert the image as a blob in the table |
| Previous Message | Zhihong Yu | 2021-04-11 23:33:52 | Re: Have I found an interval arithmetic bug? |