| From: | Surafel Temesgen <surafel3000(at)gmail(dot)com> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
| Cc: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, vik(dot)fearing(at)2ndquadrant(dot)com, Mark Dilger <hornschnorter(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, andrew(at)tao11(dot)riddles(dot)org(dot)uk |
| Subject: | Re: FETCH FIRST clause PERCENT option |
| Date: | 2019-03-26 12:06:52 |
| Message-ID: | CALAY4q9YTzGwu8sScxEKZb1sJPZg5AbXNPUwe2ydqkjT9BB+ZQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Feb 28, 2019 at 11:16 PM Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
wrote:
>
> To give you a (admittedly, somewhat contrived and artificial example):
>
> SELECT * FROM t1 WHERE id IN (
> SELECT id FROM t2 ORDER BY x FETCH FIRST 10 PERCENT ROWS ONLY
> );
>
> Maybe this example is bogus and/or does not really matter in practice. I
> don't know, but I've been unable to convince myself that's the case.
does this means we abandon incremental approach? and am not sure of
calculating
percentage after OFFSET clause is acceptable or not
regards
Surafel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2019-03-26 12:31:15 | Re: pgsql: Get rid of backtracking in jsonpath_scan.l |
| Previous Message | Dean Rasheed | 2019-03-26 11:59:56 | Re: [HACKERS] PATCH: multivariate histograms and MCV lists |