Hi,
I am very much interested in the how the partitioning of observation_fact by
concept_cd
was done.
(a) Can you share the syntax you used to create the partitions?
(b) How many partitions did you make?
Presumably the most extreme level would be one per concept-code.
How did that affect how you loaded the data? Do you have to load the
partitions separately, or does postgres determine which partition to use
based on the value of the concept_cd field?
Jay Pedersen, M.A.
Department of Pathology/Microbiology
University of Nebraska Medical Center
985900 Nebraska Medical Center
Omaha NE 68198-5900
402-559-9487<tel:402-559-9593> (office)
402-739-3496<tel:402-350-7851> (mobile)
________________________________
From: GPC Informatics <d...@madmode.com>
Sent: Thursday, April 26, 2018 10:10:04 AM
To: Narayana, Yeshwanth R; m...@wisc.edu; dconno...@kumc.edu; McClay, James C;
avall...@mcw.edu
Cc: Campbell, James R; Pedersen, Jay G
Subject: Re: [gpc-informatics] #676: Postgres SNOW SHRINE nodes (UNMC , MCW)
time out
Non-UNMC email
#676: Postgres SNOW SHRINE nodes (UNMC , MCW) time out
--------------------------+----------------------------
Reporter: ynarayana | Owner: mish
Type: problem | Status: assigned
Priority: minor | Milestone: snow-shrine-2
Component: data-sharing | Resolution:
Keywords: | Blocked By:
Blocking: |
--------------------------+----------------------------
Comment (by avallejos):
I have improved the performance of our PostreSQL node. So we should be
returning results in a timely manner.
In case anyone is curious... this was done by adding a GIN index to the
Concept_Dimension and partitioning the observation_fact table based on
concept_cd. Since we are running PostreSQL 10 we are able to use range
partitioning on the string prefix on the concept_cd value.
--
Ticket URL:
<http://informatics.gpcnetwork.org/trac/Project/ticket/676#comment:6>
gpc-informatics <http://informatics.gpcnetwork.org/>
Greater Plains Network - Informatics
The information in this e-mail may be privileged and confidential, intended
only for the use of the addressee(s) above. Any unauthorized use or disclosure
of this information is prohibited. If you have received this e-mail by mistake,
please delete it and immediately contact the sender.
_______________________________________________
Gpc-dev mailing list
Gpc-dev@listserv.kumc.edu
http://listserv.kumc.edu/mailman/listinfo/gpc-dev
