<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Roles on BonesMoses.org</title>
    <link>https://bonesmoses.org/tags/roles/</link>
    <description>Recent content in Roles on BonesMoses.org</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 31 May 2024 12:00:00 +0000</lastBuildDate><atom:link href="https://bonesmoses.org/tags/roles/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PG Phriday: Taking Postgres for GRANTed</title>
      <link>https://bonesmoses.org/2024/pg-phriday-taking-postgres-for-granted/</link>
      <pubDate>Fri, 31 May 2024 12:00:00 +0000</pubDate>
      
      <guid>https://bonesmoses.org/2024/pg-phriday-taking-postgres-for-granted/</guid>
      <description>Not every database-backed application needs to be locked down like Fort Knox. Sometimes there are even roles that leverage blanket access to large swathes of available data, if not every table, simply for auditing or monitoring purposes. Normally this would require quite a bit of preparation or ongoing privilege management, but Postgres came up with a unique solution starting with version 14: predefined roles.
This topic comes up relatively frequently in Postgres chats like Discord, Slack, and IRC.</description>
    </item>
    
    <item>
      <title>PG Phriday: Under Observation</title>
      <link>https://bonesmoses.org/2024/pg-phriday-under-observation/</link>
      <pubDate>Fri, 12 Apr 2024 16:30:04 +0000</pubDate>
      
      <guid>https://bonesmoses.org/2024/pg-phriday-under-observation/</guid>
      <description>&lt;p&gt;Have you ever wanted to use a non-superuser role in a Postgres database to perform actions that are normally restricted? Even something as simple as reading from the &lt;code&gt;pg_stat_activity&lt;/code&gt; view requires special permissions to view the &lt;code&gt;query&lt;/code&gt; column because it could contain sensitive information.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
