| From: | Surafel Temesgen <surafel3000(at)gmail(dot)com> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, andrew(at)tao11(dot)riddles(dot)org(dot)uk, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: FETCH FIRST clause WITH TIES option |
| Date: | 2019-01-02 10:51:40 |
| Message-ID: | CALAY4q8Co7-tdvK=_iuE5ua4GPE7A6mM_RMLAu7ox-Pafo8dXw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 1, 2019 at 8:38 PM Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
wrote:
> >
> > The attached patch include all the comment given by Tomas and i
> > check sql standard about LIMIT and this feature
> >
>
> Unfortunately, it seems the "limit" regression tests fail for some
> reason - the output mismatches the expected results for some reason. It
> seems as if the WITH TIES code affects ordering of the results within
> the group. See the attached file.
>
>
Yes the reason is the order of returned row is not always the same. I
remove other columns from the result set to get constant result
Regards
Surafel
| Attachment | Content-Type | Size |
|---|---|---|
| fetch_first_with_ties_v4.patch | text/x-patch | 27.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oleksii Kliukin | 2019-01-02 11:17:11 | Re: Connection slots reserved for replication |
| Previous Message | Petr Jelinek | 2019-01-02 10:02:22 | Re: Connection slots reserved for replication |