| From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
|---|---|
| To: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: AW: LIMIT in DECLARE CURSOR: request for comments |
| Date: | 2000-10-31 13:23:53 |
| Message-ID: | 3.0.5.32.20001101002353.02ab1b00@mail.rhyme.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At 14:14 31/10/00 +0100, Zeugswetter Andreas SB wrote:
>>
>> Which is why I like the client being able to ask the
>> optimizer for certain kinds of solutions *explicitly*.
>
>Yes, something like:
> set optimization to [first_rows|all_rows]
>
That's one way that is usefull for affecting all subsequent statements, but
it would be nice to also allow such things in each statement, eg. in comments:
/*++optimizer: fast_start, no_seq_scan */
select...
ie. make all settable values dynamically settable in a statement. The scope
of the settings would probably have to depend on the abilities of the
optimizer - eg. how would subselects and views be handled?
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2000-10-31 14:12:15 | Re: Re: BIT/BIT VARYING status |
| Previous Message | Zeugswetter Andreas SB | 2000-10-31 13:14:15 | AW: LIMIT in DECLARE CURSOR: request for comments |