Jira (PDB-3625) Use upsert for fact storage

[Russell Mull (JIRA)]

Russell Mull updated an issue

PuppetDB / PDB-3625 Use upsert for fact storage Change By: Russell Mull Sprint: Hopper Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

[Russell Mull (JIRA)]

Russell Mull created an issue

PuppetDB / PDB-3625 Use upsert for fact storage

Issue Type: New Feature Assignee: Unassigned Created: 2017/07/24 3:13 PM Priority: Normal Reporter: Russell Mull Storing facts currently (as of PDB 5.x) works like this: Get the value hashes for everything in the stored factset Compute the hashes for everything in the new factset Compare them Store new values for whatever is different or new Postgres 9.6 has support for upsert (INSERT ON CONFLICT UPDATE), which could let us do things better. Store all values in a single upsert statement, rather than using separate updates and inserts. We may be able to forego the local hash comparison, instead sending all values in a single upsert statement that is set up to only store values if they have changed.

Add Comment

[Russell Mull (JIRA)]

Russell Mull updated an issue

PuppetDB / PDB-3625 Use upsert for fact storage

Change By: Russell Mull Sprint: Data Platform 2017-07-27 Hopper

Add Comment

[Russell Mull (JIRA)]

Russell Mull updated an issue

PuppetDB / PDB-3625 Use upsert for fact storage

Change By: Russell Mull Sprint: Hopper Data Platform 2017-07-27

Add Comment

[Jeff Yarnell (JIRA)]

Jeff Yarnell updated an issue

PuppetDB / PDB-3625 Use upsert for fact storage

Moving from Hopper to Backlog because we believe this may be resolved by potential change to how facts are stored (which Russ is exploring now).

Add Comment

[Jeff Yarnell (JIRA)]

Jeff Yarnell updated an issue

PuppetDB / PDB-3625 Use upsert for fact storage

Change By: Jeff Yarnell Sprint: Hopper/Triage

Add Comment

[Claudia Petty (Jira)]

Claudia Petty updated an issue

PuppetDB / PDB-3625 Use upsert for fact storage

Change By: Claudia Petty Labels: new-feature

Add Comment

This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8)