From: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
---|---|
To: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, Marko Tiikkaja <marko(at)joh(dot)to> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Dave Cramer <pg(at)fastcrypt(dot)com> |
Subject: | Re: Fwd: [JDBC] Re: 9.4-1207 behaves differently with server side prepared statements compared to 9.2-1102 |
Date: | 2016-01-12 15:52:14 |
Message-ID: | CAB=Je-G-LrJwDX4HjWdtgh0HtW1w4By+DoQBEvELE7wiYBtW5g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
> I don't know if there is a good solution except disabling server prepared statements.
Why doesn't backend reuse already existing good plan?
The plan does account for the skew.
Can backend take selectivities from the original bind values?
Vladimir
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2016-01-12 15:55:47 | Re: Fwd: [JDBC] Re: 9.4-1207 behaves differently with server side prepared statements compared to 9.2-1102 |
Previous Message | Alvaro Herrera | 2016-01-12 15:51:57 | Re: Patch: fix lock contention for HASHHDR.mutex |
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2016-01-12 15:55:47 | Re: Fwd: [JDBC] Re: 9.4-1207 behaves differently with server side prepared statements compared to 9.2-1102 |
Previous Message | Albe Laurenz | 2016-01-12 14:08:14 | Re: Fwd: [JDBC] Re: 9.4-1207 behaves differently with server side prepared statements compared to 9.2-1102 |