<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    
    <title>Postgres OnLine Journal - contrib spotlight</title>
    <link>https://www.postgresonline.com/journal/</link>
    <description>Tips and tricks for PostgreSQL</description>
    <dc:language>en</dc:language>
    <generator>Serendipity 2.6.0 - http://www.s9y.org/</generator>
    <pubDate>Tue, 14 Jul 2026 20:40:20 GMT</pubDate>

    <image>
    <url>https://www.postgresonline.com/journal/templates/default/img/s9y_banner_small.png</url>
    <title>RSS: Postgres OnLine Journal - contrib spotlight - Tips and tricks for PostgreSQL</title>
    <link>https://www.postgresonline.com/journal/</link>
    <width>100</width>
    <height>21</height>
</image>

<item>
    <title>Replacing pgAgent with pg_timetable: Part 2 - Installing pg_timetable as a service in Linux </title>
    <link>https://www.postgresonline.com/journal/index.php?/archives/424-Replacing-pgAgent-with-pg_timetable-Part-2-Installing-pg_timetable-as-a-service-in-Linux.html</link>
            <category>contrib spotlight</category>
            <category>pg_timetable</category>
            <category>pgadmin</category>
            <category>pgagent</category>
    
    <comments>https://www.postgresonline.com/journal/index.php?/archives/424-Replacing-pgAgent-with-pg_timetable-Part-2-Installing-pg_timetable-as-a-service-in-Linux.html#comments</comments>
    <wfw:comment>https://www.postgresonline.com/journal/wfwcomment.php?cid=424</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>https://www.postgresonline.com/journal/rss.php?version=2.0&amp;type=comments&amp;cid=424</wfw:commentRss>
    

    <author>nospam@example.com (Leo Hsu and Regina Obe)</author>
    <content:encoded>
    &lt;p&gt;As stated in &lt;a href=&quot;https://www.postgresonline.com/journal/423-Replacing-pgAgent-with-pg_timetable-Part-1.html&quot; target=&quot;_blank&quot;&gt;Part 1, pgAgent is going away&lt;/a&gt;, so I&#039;m focussing on setting up pg_timetable as similar to pgAgent that I can.
For this second part, I&#039;m going to go over how to configure pg_timetable as a service on Linux.
&lt;/p&gt;

&lt;p&gt;A heads up, i really loved the pgAgent UI in pgAdmin so I&#039;m working on one for pg_timetable which is mostly patterned after the pgAgent one.  You can see the pull request work in progress &lt;a href=&quot;https://github.com/pgadmin-org/pgadmin4/pull/10152&quot;&gt;pg_timetable UI for pgAdmin&lt;/a&gt;. I&#039;m in the middle of cleaning up some loose ends before it is ready for commit.&lt;/p&gt; &lt;a class=&quot;block_level&quot; href=&quot;https://www.postgresonline.com/journal/index.php?/archives/424-Replacing-pgAgent-with-pg_timetable-Part-2-Installing-pg_timetable-as-a-service-in-Linux.html#extended&quot;&gt;Continue reading &quot;Replacing pgAgent with pg_timetable: Part 2 - Installing pg_timetable as a service in Linux &quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Tue, 14 Jul 2026 16:07:00 -0400</pubDate>
    <guid isPermaLink="false">https://www.postgresonline.com/journal/index.php?/archives/424-guid.html</guid>
    
</item>
<item>
    <title>http extension for windows updated to include PostgreSQL19 64-bit</title>
    <link>https://www.postgresonline.com/journal/index.php?/archives/371-http-extension-for-windows-updated-to-include-PostgreSQL19-64-bit.html</link>
            <category>10</category>
            <category>11</category>
            <category>12</category>
            <category>13</category>
            <category>14</category>
            <category>15</category>
            <category>16</category>
            <category>17</category>
            <category>18</category>
            <category>19</category>
            <category>9.4</category>
            <category>9.5</category>
            <category>9.6</category>
            <category>contrib spotlight</category>
            <category>http</category>
            <category>postgresql versions</category>
            <category>winextensions</category>
    
    <comments>https://www.postgresonline.com/journal/index.php?/archives/371-http-extension-for-windows-updated-to-include-PostgreSQL19-64-bit.html#comments</comments>
    <wfw:comment>https://www.postgresonline.com/journal/wfwcomment.php?cid=371</wfw:comment>

    <slash:comments>11</slash:comments>
    <wfw:commentRss>https://www.postgresonline.com/journal/rss.php?version=2.0&amp;type=comments&amp;cid=371</wfw:commentRss>
    

    <author>nospam@example.com (Leo Hsu and Regina Obe)</author>
    <content:encoded>
    &lt;div style=&quot;background-color:green;color:white&quot;&gt;Updated  June 21st, 2026 64-bit package for PostgreSQL 19 &lt;a href=&quot;https://github.com/pramsey/pgsql-http/releases/tag/v1.7.1&quot; target=&quot;_blank&quot; style=&#039;color:white&#039;&gt;http extension v1.7.1 release&lt;/a&gt;. &lt;/div&gt;


&lt;p&gt;For those folks on windows who want to do http gets and posts directly from your PostgreSQL server, we&#039;ve made binaries for the &lt;a href=&quot;https://github.com/pramsey/pgsql-http&quot; target=&quot;_blank&quot;&gt;http extension&lt;/a&gt; for PostgreSQL Windows.&lt;/p&gt;

&lt;p&gt;These are designed to work with PostgreSQL EDB windows distributions.&lt;/p&gt;

&lt;p&gt;If you have PostGIS already installed, many of these files you will also already have since things like the libcurl and PCRE are also packaged with PostGIS.&lt;/p&gt;

 &lt;a class=&quot;block_level&quot; href=&quot;https://www.postgresonline.com/journal/index.php?/archives/371-http-extension-for-windows-updated-to-include-PostgreSQL19-64-bit.html#extended&quot;&gt;Continue reading &quot;http extension for windows updated to include PostgreSQL19 64-bit&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Sun, 21 Jun 2026 05:10:00 -0400</pubDate>
    <guid isPermaLink="false">https://www.postgresonline.com/journal/index.php?/archives/371-guid.html</guid>
    
</item>
<item>
    <title>Replacing pgAgent with pg_timetable: Part 1</title>
    <link>https://www.postgresonline.com/journal/index.php?/archives/423-Replacing-pgAgent-with-pg_timetable-Part-1.html</link>
            <category>contrib spotlight</category>
    
    <comments>https://www.postgresonline.com/journal/index.php?/archives/423-Replacing-pgAgent-with-pg_timetable-Part-1.html#comments</comments>
    <wfw:comment>https://www.postgresonline.com/journal/wfwcomment.php?cid=423</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>https://www.postgresonline.com/journal/rss.php?version=2.0&amp;type=comments&amp;cid=423</wfw:commentRss>
    

    <author>nospam@example.com (Leo Hsu and Regina Obe)</author>
    <content:encoded>
    &lt;p&gt;pgAgent has been my go to scheduling solution for quite some time. Sadly in 6 months it will be completely retired and the pgAgent UI in pgAdmin will be gone.
The main reasons I liked pgAgent were:

&lt;ul&gt;
	&lt;li&gt;Cross Platform: I have a lot of windows and linux customers, so this was important.&lt;/li&gt;
	&lt;li&gt;Nice UI in pgAdmin, so I could do all work with PostgreSQL and schedule things at the same time as well as check status of jobs.&lt;/li&gt;
	&lt;li&gt;The database backend is PostgreSQL, my favorite database&lt;/li&gt;
	&lt;li&gt;Supports Multiple Agents with varying OS.&lt;/li&gt;
	&lt;li&gt;Supports jobs having many ordered steps&lt;/li&gt;
&lt;/ul&gt;
&lt;/p&gt; &lt;a class=&quot;block_level&quot; href=&quot;https://www.postgresonline.com/journal/index.php?/archives/423-Replacing-pgAgent-with-pg_timetable-Part-1.html#extended&quot;&gt;Continue reading &quot;Replacing pgAgent with pg_timetable: Part 1&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Sun, 21 Jun 2026 03:01:00 -0400</pubDate>
    <guid isPermaLink="false">https://www.postgresonline.com/journal/index.php?/archives/423-guid.html</guid>
    
</item>

</channel>
</rss>
