| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "'Tobias Bussmann *EXTERN*'" <t(dot)bussmann(at)gmx(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Subject: | Re: Parallel execution and prepared statements |
| Date: | 2016-12-05 10:18:55 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B5399FCDF@ntex2010i.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tobias Bussmann wrote:
>> I think if we don't see any impact then we should backpatch this
>> patch. However, if we decide to go some other way, then I can provide
>> a separate patch for back branches. BTW, what is your opinion?
>
> I could not find anything on backporting guidelines in the wiki but my opinion would be to backpatch
> the patch in total. With a different behaviour between the simple and extended query protocol it would
> be hard to debug query performance issue in user applications that uses PQprepare. If the user tries
> to replicate a query with a PREPARE in psql and tries to EXPLAIN EXECUTE it, the results would be
> different then what happens within the application. That behaviour could be confusing, like
> differences between EXPLAIN SELECT and EXPLAIN EXECUTE can be to less experienced users.
+1
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro HORIGUCHI | 2016-12-05 10:29:54 | Re: Radix tree for character conversion |
| Previous Message | Daniel Verite | 2016-12-05 09:57:24 | Re: pg_dump / copy bugs with "big lines" ? |