| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Boyko Yordanov <b(dot)yordanov2(at)gmail(dot)com> |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14020: row_number() over(partition by order by) - weird behavior |
| Date: | 2016-03-15 15:13:31 |
| Message-ID: | CAKFQuwYpQJsLWBPRoR8+tA72aCUoV8cKX6eiN5dkSLeAtSWMTg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Mar 15, 2016 at 2:04 AM, Boyko Yordanov <b(dot)yordanov2(at)gmail(dot)com>
wrote:
> Thinking further on this, I now got your point on the “duplicate
> grossprices is ordered randomly” suggestion.
>
> What I missed to realize is that the update query updates *every* product
> partition that has reordered due to duplicate grossprice being ordered
> randomly, resulting in thousands of updates instead of just < 148 (or < 99
> in the case of product = 2 partition).
>
> Is there a way to ensure persistence of “over(order by duplicate_columns)”
> ordering, except for ordering by a second (or even third) column?
>
>
No, you need to have enough columns for deterministic order.
Dave
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-03-15 16:04:48 | Re: [BUGS] BUG #14023: pq odbc driver crashed while get data from boolean column |
| Previous Message | suzhengchun | 2016-03-15 10:24:03 | BUG #14023: pq odbc driver crashed while get data from boolean column |