| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Michael Lewis <mlewis(at)entrata(dot)com>, Jonathan Marks <jonathanaverymarks(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Forcing index usage |
| Date: | 2019-04-17 17:07:25 |
| Message-ID: | 20190417170725.cg2mga5wxuwon5ds@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Apr 3, 2019 at 03:28:48PM -0400, Stephen Frost wrote:
> Greetings,
>
> * Michael Lewis (mlewis(at)entrata(dot)com) wrote:
> > Thanks for that advance warning since it is a handy option to force the
> > planning barrier in my experience. What's a resource to see other coming
> > changes in v12 especially changes to default behavior like this? Will there
> > be a new cte_collapse_limit setting or similar?
>
> Check the release notes.
Yes, once they are written in a few weeks.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Lewis | 2019-04-17 17:16:28 | Re: Forcing index usage |
| Previous Message | Bruce Momjian | 2019-04-17 17:05:08 | Re: Move vs. copy table between databases that share a tablespace? |