Re: Better tracking of free space during SP-GiST index build

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Oleg Bartunov <obartunov(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Emre Hasegeli <emre(at)hasegeli(dot)com>
Subject: Re: Better tracking of free space during SP-GiST index build
Date: 2016-09-28 23:01:56
Message-ID: CAMkU=1xEDLFU=dA8C0nEoP9BEA5ER6O5PY96X4Qmx0D+z_j_kQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 28, 2016 at 10:48 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> On Sun, Sep 25, 2016 at 3:28 PM, Tomas Vondra
> <tomas(dot)vondra(at)2ndquadrant(dot)com> wrote:
> > Sure, that would be useful.
> >
> > I think it would be useful to make repository of such data sets, so that
> > patch authors & reviewers can get a reasonable collection of data sets if
> > needed, instead of scrambling every time. Opinions?
>
> In theory, great idea. In practice, I suspect the problem will be
> that nobody will know what the use case for a particular data set was
> supposed to be, and therefore it'll become a collection of files
> nobody knows what to do with.
>

We would have to store them together with the example queries they pertain
to, somehow, rather than just a loose assemblage of files. Best case is
probably to have a generator for the data, rather than data itself, when
possible. What would be the best technology to host such a thing?

Cheers,

Jeff

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ivan Kartyshov 2016-09-28 23:45:58 Re: less expensive pg_buffercache on big shmem
Previous Message Tomas Vondra 2016-09-28 22:45:15 Re: Speed up Clog Access by increasing CLOG buffers