From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Rita <rmorgan466(at)gmail(dot)com> |
Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: using hstore to store documents |
Date: | 2017-01-26 15:38:16 |
Message-ID: | CAKFQuwbU3B51cG0yWAZvjeAvh87tpQ17f7AtgYna+m+kqkvbRA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Jan 26, 2017 at 5:37 AM, Rita <rmorgan466(at)gmail(dot)com> wrote:
> of course, sorry for being vague.
>
> I have an external process generating a XML file (every 30 secs) which is
> about 10MB. I would like to store the file as XML type for me to query
> using xpath. I plan to query it every few seconds by few hundred clients.
> so, it maybe easier for me create a separate table of my xpath results and
> have clients query that table (xpath can be expensive).
>
>
If the XML being generated has a fixed structure/schema I personally would
treat the XML as a serialization format and de-serialize and store it in a
database as one or more relationally linked tables. If you have to deal
with the possibility of dynamic structure I would still try to put the
fixed items into individual columns and then and then any dynamic items
could be stuffed into an hstore typed table.
My answer to your stated question is: what happened when you tried doing
that? Documentation and a bit of experimentation goes a long ways in
learning.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Rakesh Kumar | 2017-01-26 16:34:05 | Transaction apply speed on the standby |
Previous Message | Adrian Klaver | 2017-01-26 15:25:49 | Re: using hstore to store documents |