<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Extension on ads' corner</title><link>https://andreas.scherbaum.la/tags/extension/</link><description>Recent content in Extension on ads' corner</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 02 Jun 2025 00:00:00 +0200</lastBuildDate><atom:link href="https://andreas.scherbaum.la/tags/extension/index.xml" rel="self" type="application/rss+xml"/><item><title>Postgres Extensions Day Montréal 2025</title><link>https://andreas.scherbaum.la/post/2025-06-02_postgres-extensions-day-montreal-2025/</link><pubDate>Mon, 02 Jun 2025 00:00:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2025-06-02_postgres-extensions-day-montreal-2025/</guid><description>&lt;p&gt;On Monday before PGConf.dev, the &lt;a href="https://pgext.day/"&gt;Postgres Extensions Day 2025&lt;/a&gt; took place. Same venue, same floor. A day fully packed with talks, and interesting discussions.&lt;/p&gt;&#10;&lt;p&gt;This event shows once again that extensions in &lt;em&gt;PostgreSQL&lt;/em&gt; are thriving. It also shows that there is a lot of work to do to make extensions more usable and discoverable for users. Just a few problems which where discussed:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;A database can only load one extension version.&lt;/li&gt;&#10;&lt;li&gt;Installing a new version of an extension without upgrading all databases may or may not work: depends if the library is backwards compatible.&lt;/li&gt;&#10;&lt;li&gt;Rolling forward to a new version usually works, rolling backwardsis complicated or impossible.&lt;/li&gt;&#10;&lt;li&gt;Restoring a backup with an older version of an extension might not work.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;The event was organized by &lt;a href="https://postgresql.life/post/yurii_rashkovskii/" title="PostgreSQL Person of the Week interview with: Yurii Rashkovskii"&gt;Yurii Rashkovskii&lt;/a&gt; and &lt;a href="https://postgresql.life/post/chris_travers/" title="PostgreSQL Person of the Week interview with: Chris Travers"&gt;Chris Travers&lt;/a&gt; (who could not attend).&lt;/p&gt;</description></item><item><title>PGConf.EU 2024 Review</title><link>https://andreas.scherbaum.la/post/2024-12-13_pgconf-eu-2024-review/</link><pubDate>Fri, 13 Dec 2024 00:00:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2024-12-13_pgconf-eu-2024-review/</guid><description>&lt;p&gt;&lt;em&gt;PGConf.EU 2024&lt;/em&gt; in &lt;em&gt;Athens&lt;/em&gt; is over, time for a review - which is long overdue. With 782 confirmed registrations, it was the largest &lt;em&gt;PostgreSQL&lt;/em&gt; conference organized by &lt;em&gt;PostgreSQL Europe&lt;/em&gt; - so far. And maybe the largest in-person &lt;em&gt;PostgreSQL&lt;/em&gt; community conference world-wide.&lt;/p&gt;&#10;&lt;p&gt;If you see me writing about &amp;ldquo;us&amp;rdquo;, that&amp;rsquo;s because I&amp;rsquo;m one of the &lt;a href="https://2024.pgconf.eu/organisation/"&gt;organizers&lt;/a&gt; of this conference.&lt;/p&gt;&#10;&lt;p&gt;The format was mostly the same as in previous years: Tuesday was training day, provided by sponsors. Wednesday, Thursday and Friday has seen three regular tracks with talks, and one track with sponsor talks. In my opinion, the sponsors do a good job submitting interesting talks for the sponsor track, and are not just doing yet another product presentation. This shows that everyone takes the sponsor track seriously, and it is a good addition to the talks in the main tracks.&lt;/p&gt;</description></item><item><title>PostgreSQL Development Conference 2024 - Review</title><link>https://andreas.scherbaum.la/post/2024-06-14_postgresql-development-conference-2024-review/</link><pubDate>Fri, 14 Jun 2024 02:00:25 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2024-06-14_postgresql-development-conference-2024-review/</guid><description>&lt;p&gt;This year&amp;rsquo;s &lt;em&gt;PGCon&lt;/em&gt; was different. For starters, the conference is renamed to &lt;em&gt;PGConf.dev&lt;/em&gt;, and it no longer takes place in &lt;em&gt;Ottawa&lt;/em&gt;, but in &lt;em&gt;Vancouver, BC&lt;/em&gt;. It&amp;rsquo;s also a new team which organized the conference, and they did a superb job!&lt;/p&gt;</description></item><item><title>Firefox Multi-Account Container Extension: Separate containers and cookies for websites</title><link>https://andreas.scherbaum.la/post/2024-05-03_firefox-multi-account-container-extension-separate-containers-and-cookies-for-websites/</link><pubDate>Fri, 03 May 2024 10:50:48 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2024-05-03_firefox-multi-account-container-extension-separate-containers-and-cookies-for-websites/</guid><description>&lt;p&gt;&lt;em&gt;Firefox&lt;/em&gt; is very extensible, and the app store has a large number of extensions one can install.&lt;/p&gt;&#10;&lt;p&gt;One of these extensions is the &lt;a href="https://addons.mozilla.org/en-US/firefox/addon/multi-account-containers/"&gt;Multi-Account-Container plugin&lt;/a&gt;, which allows users to separate websites from each other. What it does is creating a separate environment for all the cookies, you get a separate instance of the browser in every container you create.&lt;/p&gt;&#10;&lt;p&gt;That is very useful to containerise websites which like to track visitors everywhere, like Facebook as example. You create one container for Facebook, where you login into your account. And outside of this container you are not logged in, as far as Facebook is concerned.&lt;/p&gt;</description></item></channel></rss>