From: | Mark Moellering <markmoellering(at)psyberation(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Where **not** to use PostgreSQL? |
Date: | 2019-02-28 13:59:43 |
Message-ID: | CAA0uU3UXqe7SSEPFWAq42Y6Lj2vg+++30f7LUkEq56rWec4mnw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I wish more people would ask this question, to me, it is the true mark of
experience. In general, I think of PostgreSQL as the leading Relational
Database. The farther you get away from relational data and relational
queries, the more I would say, you should look for other products or
solutions. But if you want to store relational data and then run queries
over it, then stick with PostgreSQL.
My 2 scents..
Mark
On Thu, Feb 28, 2019 at 8:28 AM Nicolas Grilly <nicolas(at)gardentechno(dot)com>
wrote:
> On Thu, Feb 28, 2019 at 2:12 PM Chris Travers <chris(dot)travers(at)gmail(dot)com>
> wrote:
>
>> Where I did this on the TB scale, we had some sort of ranking but it was
>> not based on ts_rank.
>>
>> On the PB scale systems I work on now, it is distributed, and we don't
>> order in PostgreSQL (or anywhere else, though if someone wants to write to
>> disk and sort, they can do this I guess)
>>
>
> Thanks!
>
>>
From | Date | Subject | |
---|---|---|---|
Next Message | Andy Fan | 2019-02-28 14:55:54 | Re: create unique constraint on jsonb->filed during create table |
Previous Message | Nicolas Grilly | 2019-02-28 13:27:27 | Re: Where **not** to use PostgreSQL? |