Add notes for 2018-06-24

content/posts/2018-06.md

@@ -227,4 +227,20 @@ UPDATE 1
 - I uploaded the twenty-four reports to the IWMI Reports collection: https://cgspace.cgiar.org/handle/10568/36188
 - I uploaded the seventy-six book chapters to the IWMI Book Chapters collection: https://cgspace.cgiar.org/handle/10568/36178
 
+## 2018-06-24
+
+- I was restoring a PostgreSQL dump on my test machine and found a way to restore the CGSpace dump as the `postgres` user, but have the owner of the schema be the `dspacetest` user:
+
+```
+$ dropdb -h localhost -U postgres dspacetest
+$ createdb -h localhost -U postgres -O dspacetest --encoding=UNICODE dspacetest
+$ psql -h localhost -U postgres dspacetest -c 'alter user dspacetest superuser;'
+$ pg_restore -h localhost -U postgres -d dspacetest -O --role=dspacetest -W -h localhost /tmp/cgspace_2018-06-24.backup
+$ psql -h localhost -U postgres dspacetest -c 'alter user dspacetest nosuperuser;'
+```
+
+- The `-O` option to `pg_restore` makes the import process ignore ownership specified in the dump itself, and instead makes the schema owned by the user doing the restore
+- I always prefer to use the `postgres` user locally because it's just easier than remembering the `dspacetest` user's password, but then I couldn't figure out why the resulting schema was owned by `postgres`
+- So with this you connect as the `postgres` superuser and then switch roles to `dspacetest` (also, make sure this user has `superuser` privileges before the restore)
+
 <!-- vim: set sw=2 ts=2: -->

docs/2018-06/index.html

@@ -41,7 +41,7 @@ sys     2m7.289s
 
 <meta property="article:published_time" content="2018-06-04T19:49:54-07:00"/>
 
-<meta property="article:modified_time" content="2018-06-14T12:40:42&#43;03:00"/>
+<meta property="article:modified_time" content="2018-06-14T14:46:09&#43;03:00"/>
 
 
 
@@ -93,9 +93,9 @@ sys     2m7.289s
   "@type": "BlogPosting",
   "headline": "June, 2018",
   "url": "https://alanorth.github.io/cgspace-notes/2018-06/",
-  "wordCount": "1637",
+  "wordCount": "1814",
   "datePublished": "2018-06-04T19:49:54-07:00",
-  "dateModified": "2018-06-14T12:40:42&#43;03:00",
+  "dateModified": "2018-06-14T14:46:09&#43;03:00",
   "author": {
     "@type": "Person",
     "name": "Alan Orth"
@@ -427,6 +427,25 @@ UPDATE 1
 <li>I uploaded the seventy-six book chapters to the IWMI Book Chapters collection: <a href="https://cgspace.cgiar.org/handle/10568/36178">https://cgspace.cgiar.org/handle/10568/36178</a></li>
 </ul>
 
+<h2 id="2018-06-24">2018-06-24</h2>
+
+<ul>
+<li>I was restoring a PostgreSQL dump on my test machine and found a way to restore the CGSpace dump as the <code>postgres</code> user, but have the owner of the schema be the <code>dspacetest</code> user:</li>
+</ul>
+
+<pre><code>$ dropdb -h localhost -U postgres dspacetest
+$ createdb -h localhost -U postgres -O dspacetest --encoding=UNICODE dspacetest
+$ psql -h localhost -U postgres dspacetest -c 'alter user dspacetest superuser;'
+$ pg_restore -h localhost -U postgres -d dspacetest -O --role=dspacetest -W -h localhost /tmp/cgspace_2018-06-24.backup
+$ psql -h localhost -U postgres dspacetest -c 'alter user dspacetest nosuperuser;'
+</code></pre>
+
+<ul>
+<li>The <code>-O</code> option to <code>pg_restore</code> makes the import process ignore ownership specified in the dump itself, and instead makes the schema owned by the user doing the restore</li>
+<li>I always prefer to use the <code>postgres</code> user locally because it&rsquo;s just easier than remembering the <code>dspacetest</code> user&rsquo;s password, but then I couldn&rsquo;t figure out why the resulting schema was owned by <code>postgres</code></li>
+<li>So with this you connect as the <code>postgres</code> superuser and then switch roles to <code>dspacetest</code> (also, make sure this user has <code>superuser</code> privileges before the restore)</li>
+</ul>
+
 <!-- vim: set sw=2 ts=2: -->
 
   

docs/robots.txt

@@ -36,7 +36,7 @@ Disallow: /cgspace-notes/2015-12/
 Disallow: /cgspace-notes/2015-11/
 Disallow: /cgspace-notes/
 Disallow: /cgspace-notes/categories/
-Disallow: /cgspace-notes/tags/notes/
 Disallow: /cgspace-notes/categories/notes/
+Disallow: /cgspace-notes/tags/notes/
 Disallow: /cgspace-notes/posts/
 Disallow: /cgspace-notes/tags/

docs/sitemap.xml

@@ -4,7 +4,7 @@
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/2018-06/</loc>
-    <lastmod>2018-06-14T12:40:42+03:00</lastmod>
+    <lastmod>2018-06-14T14:46:09+03:00</lastmod>
   </url>
   
   <url>
@@ -169,7 +169,7 @@
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/</loc>
-    <lastmod>2018-06-14T12:40:42+03:00</lastmod>
+    <lastmod>2018-06-14T14:46:09+03:00</lastmod>
     <priority>0</priority>
   </url>
   
@@ -178,27 +178,27 @@
     <priority>0</priority>
   </url>
   
-  <url>
-    <loc>https://alanorth.github.io/cgspace-notes/tags/notes/</loc>
-    <lastmod>2018-06-14T12:40:42+03:00</lastmod>
-    <priority>0</priority>
-  </url>
-  
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/categories/notes/</loc>
     <lastmod>2018-03-09T22:10:33+02:00</lastmod>
     <priority>0</priority>
   </url>
   
+  <url>
+    <loc>https://alanorth.github.io/cgspace-notes/tags/notes/</loc>
+    <lastmod>2018-06-14T14:46:09+03:00</lastmod>
+    <priority>0</priority>
+  </url>
+  
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/posts/</loc>
-    <lastmod>2018-06-14T12:40:42+03:00</lastmod>
+    <lastmod>2018-06-14T14:46:09+03:00</lastmod>
     <priority>0</priority>
   </url>
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/tags/</loc>
-    <lastmod>2018-06-14T12:40:42+03:00</lastmod>
+    <lastmod>2018-06-14T14:46:09+03:00</lastmod>
     <priority>0</priority>
   </url>