Re: Better tracking of free space during SP-GiST index build - Mailing list pgsql-hackers

From Jeff Janes
Subject Re: Better tracking of free space during SP-GiST index build
Date
Msg-id CAMkU=1xEDLFU=dA8C0nEoP9BEA5ER6O5PY96X4Qmx0D+z_j_kQ@mail.gmail.com
Whole thread Raw
In response to Re: Better tracking of free space during SP-GiST index build  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Wed, Sep 28, 2016 at 10:48 AM, Robert Haas <robertmhaas@gmail.com> wrote:
On Sun, Sep 25, 2016 at 3:28 PM, Tomas Vondra
<tomas.vondra@2ndquadrant.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

pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: Speed up Clog Access by increasing CLOG buffers
Next
From: Ivan Kartyshov
Date:
Subject: Re: less expensive pg_buffercache on big shmem