Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

agnos.is Forums

  1. Home
  2. Programmer Humor
  3. The query speed isn't quite there but I would say it's close enough for a lot of purposes, especially with proper indexing.

The query speed isn't quite there but I would say it's close enough for a lot of purposes, especially with proper indexing.

Scheduled Pinned Locked Moved Programmer Humor
1 Posts 1 Posters 0 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J This user is from outside of this forum
    J This user is from outside of this forum
    [email protected]
    wrote last edited by
    #1

    The query speed isn't quite there but I would say it's close enough for a lot of purposes, especially with proper indexing. And JSON column fields are indexable. Two things I've used Postgres' JSON functionality for are:

    1.) Storing unstructured data.
    2.) Storing structured data that would exceed the table column limit.

    In both cases, I've typically needed to extract the relevant data from the JSON records to either be stored in another table of turned into a materialized view so live query performance on the JSON columns was not that important.

    1 Reply Last reply
    1
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups