| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgsql: Make heap TID a tiebreaker nbtree index column. |
| Date: | 2019-03-22 17:17:31 |
| Message-ID: | CAH2-Wz=wyWw+wwQEKJdx-DpWbnu+Hsfd1=mxnBMtYJnWEYSJaQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On Fri, Mar 22, 2019 at 9:32 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Apparently, that case is indeed unstable, cf
>
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fulmar&dt=2019-03-22%2016%3A15%3A14
I had a feeling that that would happen.
> I'm fairly baffled as to why the output order would be unstable
> given the sort, and even more as to why the instability didn't
> emerge before. Any thoughts?
DROP ROLE seems to be where all the remaining problems were, and the
order in the regression tests didn't change back to the old order when
you pushed the change to DROP OWNED BY. Something seemed amiss to me
for these reasons.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2019-03-22 17:23:58 | Re: pgsql: Make heap TID a tiebreaker nbtree index column. |
| Previous Message | Tom Lane | 2019-03-22 17:13:03 | Re: pgsql: Make heap TID a tiebreaker nbtree index column. |