tnolet · June 27, 2024 22:28 · Oct 24, 2013 · Oct 24, 2013 · Oct 24, 2013 · Oct 24, 2013
diff --git a/puppetdb_postgres_hacks.md b/puppetdb_postgres_hacks.md
@@ -116,7 +116,7 @@ Or, for example, get all the eth1 addresses for all nodes starting with dummy*:
 
 Update some facts:
 
-    update certname_facts set value = '634.64 MB' where name = 'memorysize' and certname like 'dummy%';
+    UPDATE certname_facts SET value = '634.64 MB' WHERE name = 'memorysize' AND certname LIKE 'dummy%';
 
 
 
diff --git a/puppetdb_postgres_hacks.md b/puppetdb_postgres_hacks.md
@@ -114,5 +114,9 @@ Or, for example, get all the eth1 addresses for all nodes starting with dummy*:
      10.20.1.0
      10.20.1.0
 
+Update some facts:
+
+    update certname_facts set value = '634.64 MB' where name = 'memorysize' and certname like 'dummy%';
+
 
 
diff --git a/puppetdb_postgres_hacks.md b/puppetdb_postgres_hacks.md
@@ -1,4 +1,4 @@
-**NB**: The following examples where done on Puppet Enterprise 3.0. Should be similar for OS versions, except for some file locations.
+**NB**: The following examples where done on Puppet Enterprise 3.0 running on Centos 6. Should be similar for open source versions, except for some file locations.
 
 ### 1. Logging into the PuppetDB PostgresQL database on Linux
 

diff --git a/gistfile1.md → puppetdb_postgres_hacks.md b/gistfile1.md → puppetdb_postgres_hacks.md
diff --git a/puppetdb postgres hacks → gistfile1.md b/puppetdb postgres hacks → gistfile1.md
diff --git a/gistfile1.md → puppetdb postgres hacks b/gistfile1.md → puppetdb postgres hacks
diff --git a/gistfile1.md b/gistfile1.md
@@ -93,5 +93,26 @@ Then use that hash to get the resources:
 or in a one-liner:
 
     SELECT title FROM catalog_resources INNER JOIN certname_catalogs ON catalog_resources.catalog = certname_catalogs.catalog WHERE certname_catalogs.certname = 'agent';
+
+## 3. Same thing, but now with facts
+
+Get some nice fact data, or manipulate it for testing or modelling:
+
+    SELECT * FROM certname_facts WHERE certname = 'agent';
+
+Or, for example, get all the eth1 addresses for all nodes starting with dummy*:
+
+    pe-puppetdb=# SELECT value FROM certname_facts WHERE name = 'network_eth1' AND certname LIKE 'dummy%';
+       value
+    -----------
+     10.20.1.0
+     10.20.1.0
+     10.20.1.0
+     10.20.1.0
+     10.20.1.0
+     10.20.1.0
+     10.20.1.0
+     10.20.1.0
+
 
 
diff --git a/gistfile1.md b/gistfile1.md
@@ -38,7 +38,7 @@ a. List all tables:
 
 b. Get all nodes:
 
-    pe-puppetdb=# select * from certnames;
+    pe-puppetdb=# SELECT * FROM certnames;
         name    | deactivated
     ------------+-------------
      agent      |
@@ -48,4 +48,50 @@ b. Get all nodes:
      dummy25    |
     ...
 
-b. 
+c. Get some resources for a specific node. First get the catalog hash for a node:
+
+    pe-puppetdb=# SELECT catalog FROM certname_catalogs WHERE certname = 'agent';
+                     catalog
+    ------------------------------------------
+     42115d6afda63764e16536153441f55efd83c8f4
+
+Then use that hash to get the resources:
+
+    pe-puppetdb=# SELECT title FROM catalog_resources WHERE catalog = '42115d6afda63764e16536153441f55efd83c8f4';
+                                   title
+    --------------------------------------------------------------------
+     peadmin-public.pem
+     /etc/puppetlabs/mcollective/ssl/clients
+     pe-mcollective-metadata
+     Settings
+     /opt/puppet/libexec/mcollective/mcollective/agent/puppetd.rb
+     default
+     /etc/puppetlabs/mcollective/ssl
+     /etc/puppetlabs/mcollective/ssl/clients/mcollective-public.pem
+     Pe_mcollective::Server::Plugins
+     Pe_mcollective::Shared_key_files
+     /opt/puppet/libexec/mcollective/mcollective/agent/puppetd.ddl
+     Pe_mcollective
+     main
+     /etc/puppetlabs/mcollective/server.cfg
+     Pe_mcollective::Server
+     Pe_mcollective::Params
+     mcollective-private.pem
+     pe-mcollective
+     main
+     /opt/puppet/libexec/mcollective/mcollective
+     /opt/puppet/libexec/mcollective/mcollective/application/puppetd.rb
+     mcollective-cacert.pem
+     /opt/puppet/sbin/refresh-mcollective-metadata
+     main
+     mcollective-cert.pem
+     Pe_mcollective::Role::Agent
+     puppet-dashboard-public.pem
+     mcollective-public.pem
+    (28 rows)
+
+or in a one-liner:
+
+    SELECT title FROM catalog_resources INNER JOIN certname_catalogs ON catalog_resources.catalog = certname_catalogs.catalog WHERE certname_catalogs.certname = 'agent';
+
+
diff --git a/gistfile1.md b/gistfile1.md
@@ -15,14 +15,37 @@ The easiest way to snoop around in de actual PuppetDB postgres database is using
 
 ### 2. Snooping around the data
 
-Using the REST interface is the way to go, but for some testing purposes I needed to check and/or manipulate some data. Just use the `psql` console for this.
+Using the REST interface is the way to go, but for some testing purposes I needed to check and/or manipulate some data. Just use the `psql` console for this:
+
+a. List all tables:
+
+    pe-puppetdb=# \d
+                       List of relations
+     Schema |          Name           | Type  |    Owner
+    --------+-------------------------+-------+-------------
+     public | catalog_resources       | table | pe-puppetdb
+     public | catalogs                | table | pe-puppetdb
+     public | certname_catalogs       | table | pe-puppetdb
+     public | certname_facts          | table | pe-puppetdb
+     public | certname_facts_metadata | table | pe-puppetdb
+     public | certnames               | table | pe-puppetdb
+     public | edges                   | table | pe-puppetdb
+     public | reports                 | table | pe-puppetdb
+     public | resource_events         | table | pe-puppetdb
+     public | resource_params         | table | pe-puppetdb
+     public | schema_migrations       | table | pe-puppetdb
+
+
+b. Get all nodes:
 
     pe-puppetdb=# select * from certnames;
-    name    | deactivated
+        name    | deactivated
     ------------+-------------
      agent      |
      dummy174   |
      dummy76    |
      agent2     |
      dummy25    |
+    ...
 
+b. 
diff --git a/gistfile1.md b/gistfile1.md
@@ -1,6 +1,6 @@
 **NB**: The following examples where done on Puppet Enterprise 3.0. Should be similar for OS versions, except for some file locations.
 
-### Logging into the PuppetDB PostgresQL database on Linux
+### 1. Logging into the PuppetDB PostgresQL database on Linux
 
 The easiest way to snoop around in de actual PuppetDB postgres database is using the command prompt. You have to be the peadmin user though. Couldn't get it working just under root.
 
@@ -12,3 +12,17 @@ The easiest way to snoop around in de actual PuppetDB postgres database is using
     pe-postgres=# \c pe-puppetdb
     You are now connected to database "pe-puppetdb" as user "pe-postgres".
     pe-puppetdb=#
+
+### 2. Snooping around the data
+
+Using the REST interface is the way to go, but for some testing purposes I needed to check and/or manipulate some data. Just use the `psql` console for this.
+
+    pe-puppetdb=# select * from certnames;
+    name    | deactivated
+    ------------+-------------
+     agent      |
+     dummy174   |
+     dummy76    |
+     agent2     |
+     dummy25    |
+
diff --git a/gistfile1.md b/gistfile1.md
@@ -1,6 +1,6 @@
 **NB**: The following examples where done on Puppet Enterprise 3.0. Should be similar for OS versions, except for some file locations.
 
-## Logging into the PuppetDB PostgresQL database on Linux
+### Logging into the PuppetDB PostgresQL database on Linux
 
 The easiest way to snoop around in de actual PuppetDB postgres database is using the command prompt. You have to be the peadmin user though. Couldn't get it working just under root.
 

diff --git a/gistfile1.md b/gistfile1.md
@@ -1,14 +1,14 @@
 **NB**: The following examples where done on Puppet Enterprise 3.0. Should be similar for OS versions, except for some file locations.
 
-# Logging into the PuppetDB PostgresQL database on Linux
+## Logging into the PuppetDB PostgresQL database on Linux
 
 The easiest way to snoop around in de actual PuppetDB postgres database is using the command prompt. You have to be the peadmin user though. Couldn't get it working just under root.
 
-  [root@master bin]# sudo su - pe-postgres -s /bin/bash
-  -bash-4.1$ /opt/puppet/bin/psql
-  psql (9.2.4)
-  Type "help" for help.
-
-  pe-postgres=# \c pe-puppetdb
-  You are now connected to database "pe-puppetdb" as user "pe-postgres".
-  pe-puppetdb=#
+    [root@master bin]# sudo su - pe-postgres -s /bin/bash
+    -bash-4.1$ /opt/puppet/bin/psql
+    psql (9.2.4)
+    Type "help" for help.
+    
+    pe-postgres=# \c pe-puppetdb
+    You are now connected to database "pe-puppetdb" as user "pe-postgres".
+    pe-puppetdb=#
diff --git a/gistfile1.md b/gistfile1.md
@@ -0,0 +1,14 @@
+**NB**: The following examples where done on Puppet Enterprise 3.0. Should be similar for OS versions, except for some file locations.
+
+# Logging into the PuppetDB PostgresQL database on Linux
+
+The easiest way to snoop around in de actual PuppetDB postgres database is using the command prompt. You have to be the peadmin user though. Couldn't get it working just under root.
+
+  [root@master bin]# sudo su - pe-postgres -s /bin/bash
+  -bash-4.1$ /opt/puppet/bin/psql
+  psql (9.2.4)
+  Type "help" for help.
+
+  pe-postgres=# \c pe-puppetdb
+  You are now connected to database "pe-puppetdb" as user "pe-postgres".
+  pe-puppetdb=#