Re: Why we lost Uber as a user

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru>, Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Why we lost Uber as a user
Date: 2016-08-03 07:20:46
Message-ID: CANP8+jJYJUCr5L_gAkdtjZ_1s3py+GsYS5NoV+mejx=s0YaSWw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 29 July 2016 at 15:44, Stephen Frost <sfrost(at)snowman(dot)net> wrote:

> All very hand-wavy, of course, and it'd make sense to make the concept
> work for BRIN before we consider anything else, but it seems like there
> could be a use-case for allowing indexes other than BRIN to be built in
> a way that allows HOT updates to happen, thus eliminating the cost of
> having to update those indexes when the tuple is changed, in many cases.
> Of course, those indexes couldn't be used UNIQUE indexes or used for
> primary keys, and adjusting the parameters to a BRIN index you could
> possibly get a similar index, but this might allow such an index to
> still be usable for index-only scans, which a BRIN index will never be
> able to provide.

This idea is vaguely similar to the concepts I've been working on,
based on earlier work in 2007.

I'm starting a new post for a full discussion.

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2016-08-03 07:20:49 Lossy Index Tuple Enhancement (LITE)
Previous Message Michael Paquier 2016-08-03 06:08:58 Re: Way to access LSN (for each transaction) by directly talking to postgres?