"Neil Conway" <neilc(at)samurai(dot)com> wrote
>
> This would also be useful when diagnosing bad query plans: for example,
> setting enable_seqscan=false often causes the planner to disregard the
> use of *any* sequential scan, anywhere in the plan. The ability to
> slightly bump up the cost of particular operations would allow more
> alternative plans to be examined.
>
This method also has the problem of "enable_seqscan=false" in some
situations. I would vote we implement the final general solution like query
plan hints directly.
Regards,
Qingqing
In response to
Responses
pgsql-hackers by date
| Next: | From: Qingqing Zhou | Date: 2005-12-01 17:52:48 |
| Subject: Re: [PATCHES] A couple of proposed pgbench changes |
| Previous: | From: Richard Huxton | Date: 2005-12-01 17:25:22 |
| Subject: Re: 8.1, OID's and plpgsql |