Search Postgresql Archives

Re: Best practices for aggregate table design

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Best practices for aggregate table design
From: Vick Khera <vivek@xxxxxxxxx>
Date: Thu, 8 Oct 2015 08:12:20 -0400
In-reply-to: <87bnc9ol55.fsf@hf.protecting.net>

On Thu, Oct 8, 2015 at 3:49 AM, <hari.fuchs@xxxxxxxxx> wrote:

Is there an advantage of hstore vs. json/jsonb?

Definitely over json because that is not indexable. I'm not seeing an advantage over jsonb unless you want to prevent storing complex data structures.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- Best practices for aggregate table design
  - From: droberts
- Re: Best practices for aggregate table design
  - From: David G. Johnston
- Re: Best practices for aggregate table design
  - From: droberts
- Re: Best practices for aggregate table design
  - From: John R Pierce
- Re: Best practices for aggregate table design
  - From: David G. Johnston
- Re: Best practices for aggregate table design
  - From: droberts
- Re: Best practices for aggregate table design
  - From: Thomas Kellerer
- Re: Best practices for aggregate table design
  - From: hari . fuchs

Prev by Date: Re: dubious optimization of the function in SELECT INTO target list
Next by Date: Re: Issues with german locale on CentOS 5,6,7
Previous by thread: Re: Best practices for aggregate table design
Next by thread: Re: Best practices for aggregate table design
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux