The one with a placeholder is "more efficient" in that it pre-plans the execution before knowing what value will be stuffed into the placeholder. Unfortunately, without that information, the resulting plan sucks. [By pre-planning at prepare() time, it doesn't have to waste time re-planning every time you execute() the same prepared query.]
I have yet to run into a situation where I had and actually kept "server-side prepare" enabled, despite lots of people wanting to crow about how prepare + placeholders can be such a performance "win".
Luckily, it is easy to disable server-side prepare so that you can still use place-holders while still getting "late" query planning every time you execute(). See pg_server_prepare since we are talking Postgresql.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||