Re: kind of a bag of attributes in a DB . . . - Mailing list pgsql-general

From Chris Travers
Subject Re: kind of a bag of attributes in a DB . . .
Date
Msg-id CAKt_ZfuKFNy8cXj2fc5_5Deh6eiNHCMexgqaTMuW-Qd5B=pP9g@mail.gmail.com
Whole thread Raw
In response to kind of a bag of attributes in a DB . . .  (Albretch Mueller <lbrtchx@gmail.com>)
List pgsql-general


On Sat, Sep 7, 2019 at 5:17 PM Albretch Mueller <lbrtchx@gmail.com> wrote:
Say, you get lots of data and their corresponding metadata, which in
some cases may be undefined or undeclared (left as an empty string).
Think of youtube json files or the result of the "file" command.

I need to be able to "instantly" search that metadata and I think DBs
are best for such jobs and get some metrics out of it.

I know this is not exactly a kosher way to deal with data which can't
be represented in a nice tabular form, but I don't find the idea that
half way off either.

What is the pattern, anti-pattern or whatever relating to such design?

Do you know of such implementations with such data?

We do the debug logs of JSONB with some indexing.    It works in some limited cases but you need to have a good sense of index possibilities and how the indexes actually work.


lbrtchx




--
Best Wishes,
Chris Travers

Efficito:  Hosted Accounting and ERP.  Robust and Flexible.  No vendor lock-in.

pgsql-general by date:

Previous
From: Jim Finnerty
Date:
Subject: Whan is it safe to mark a function PARALLEL SAFE?
Next
From: rob stone
Date:
Subject: Re: How to access Postgres .pgpass file from php?