| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Hints proposal |
| Date: | 2006-10-12 16:42:55 |
| Message-ID: | 1160671375.31966.84.camel@dogma.v10.wvs |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
On Thu, 2006-10-12 at 10:14 -0500, Jim C. Nasby wrote:
> The syntax these hints is something arbitrary. I'm borrowing Oracle's
> idea of embedding hints in comments, but we can use some other method if
> desired. Right now I'm more concerned with getting the general idea
> across.
>
Is there any advantage to having the hints in the queries? To me that's
asking for trouble with no benefit at all. It would seem to me to be
better to have a system catalog that defined hints as something like:
"If user A executes a query matching regex R, then coerce (or force) the
planner in this way."
I'm not suggesting that we do that, but it seems better then embedding
the hints in the queries themselves.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Weslee Bilodeau | 2006-10-12 16:42:58 | Re: Getting the type Oid in a CREATE TYPE output function |
| Previous Message | Josh Berkus | 2006-10-12 16:40:30 | Re: [HACKERS] Hints proposal |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2006-10-12 16:45:23 | Re: [HACKERS] Hints proposal |
| Previous Message | Josh Berkus | 2006-10-12 16:40:30 | Re: [HACKERS] Hints proposal |