<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>pgloader</title>
    <link>https://pgloader.io/</link>
    <description>Recent content on pgloader</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 10 Jan 2018 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://pgloader.io/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Migrating to PostgreSQL, the White Paper</title>
      <link>https://pgloader.io/blog/migrating-to-postgresql-the-white-paper/</link>
      <pubDate>Wed, 10 Jan 2018 00:00:00 +0000</pubDate>
      <guid>https://pgloader.io/blog/migrating-to-postgresql-the-white-paper/</guid>
      <description>&lt;p&gt;After having been involved in many migration projects in the last 10 years,&#xA;I decided to publish the following &lt;a href=&#34;https://pgloader.io/white-paper&#34;&gt;White Paper&lt;/a&gt; in order to&#xA;share my learnings.&lt;/p&gt;&#xA;&lt;p&gt;The paper is titled &lt;em&gt;Migrating to PostgreSQL, Tools and Methodology&lt;/em&gt; and&#xA;proposed the &lt;strong&gt;Continuous Migration&lt;/strong&gt; approach. Get the book now:&lt;/p&gt;&#xA;&lt;script src=&#34;https://forms.convertkit.com/322615?v=6&#34;&gt;&lt;/script&gt;&lt;div data-formkit-id=&#34;_ck_322615&#34;&gt;&lt;/div&gt;&#xA;&lt;p&gt;Continuous Migration makes it easy to make incremental progress over a&#xA;period of time, and also to pause and resume the migration work later on,&#xA;should you need to do that. The method is pretty simple — just follow those&#xA;steps:&lt;/p&gt;</description>
    </item>
    <item>
      <title>About</title>
      <link>https://pgloader.io/about/</link>
      <pubDate>Thu, 21 Dec 2017 00:00:00 +0000</pubDate>
      <guid>https://pgloader.io/about/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://github.com/dimitri/pgloader&#34;&gt;pgloader&lt;/a&gt; loads data into PostgreSQL.&#xA;It knows how to load data from several kinds of &lt;em&gt;source&lt;/em&gt;:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Files&lt;/li&gt;&#xA;&lt;li&gt;Live Databases&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;Let&amp;rsquo;s dive into those two different behaviours of pgloader, starting with&#xA;its support for migrating a whole database from a connection string.&lt;/p&gt;&#xA;&lt;h1 id=&#34;loading-data-from-files&#34;&gt;Loading data from Files&lt;/h1&gt;&#xA;&lt;p&gt;You might have to process huge CSV files from time to time. For example if&#xA;you&amp;rsquo;re in the &lt;em&gt;telco&lt;/em&gt; business, those might be &lt;em&gt;Call Detail Records&lt;/em&gt;. When&#xA;using PostgreSQL the best way to load CSV files is the COPY command and&#xA;protocol, as read in the article entitled &lt;a href=&#34;https://www.citusdata.com/blog/2017/11/08/faster-bulk-loading-in-postgresql-with-copy/&#34;&gt;Faster bulk loading in Postgres&#xA;with&#xA;copy&lt;/a&gt;&#xA;from Craig Kerstiens.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Continuous Migration</title>
      <link>https://pgloader.io/blog/continuous-migration/</link>
      <pubDate>Thu, 21 Dec 2017 00:00:00 +0000</pubDate>
      <guid>https://pgloader.io/blog/continuous-migration/</guid>
      <description>&lt;!-- raw HTML omitted --&gt;&#xA;&lt;p&gt;After having been involved in many migration projects over the last 10&#xA;years, I decided to publish the following &lt;a href=&#34;https://pgloader.io/white-paper&#34;&gt;White&#xA;Paper&lt;/a&gt; in order to share my learnings.&lt;/p&gt;&#xA;&lt;p&gt;The paper is titled &lt;a href=&#34;https://pgloader.io/white-paper&#34;&gt;Migrating to PostgreSQL, Tools and&#xA;Methodology&lt;/a&gt; and details the &lt;strong&gt;Continuous&#xA;Migration&lt;/strong&gt; approach. It describes how to migrate from another relational&#xA;database server technology to PostgreSQL. The reasons to do so are many, and&#xA;first among them is often the licensing model.&lt;/p&gt;</description>
    </item>
    <item>
      <title>pgloader, Your Migration Companion</title>
      <link>https://pgloader.io/blog/pgloader-your-migration-companion/</link>
      <pubDate>Mon, 30 Oct 2017 00:00:00 +0000</pubDate>
      <guid>https://pgloader.io/blog/pgloader-your-migration-companion/</guid>
      <description>&lt;h1 id=&#34;postgresql-conference-europe-2017&#34;&gt;PostgreSQL Conference Europe 2017&lt;/h1&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://2017.pgconf.eu/&#34;&gt;PGConf.EU&lt;/a&gt; is a unique chance for European&#xA;PostgreSQL users and developers to catch up, learn, build relationships, get&#xA;to know each other and consolidate a real network of professionals that use&#xA;and work with PostgreSQL.&lt;/p&gt;&#xA;&lt;h1 id=&#34;pgloader-your-migration-companion&#34;&gt;pgloader, your migration companion&lt;/h1&gt;&#xA;&lt;p&gt;Migrating data from another RDBMS to PostgreSQL should be really easy. After&#xA;all it’s all relations and tables and the same data types everywhere or&#xA;abouts, with text, dates and numbers. Well it’s actually quite messy and&#xA;complex to migrate the data properly from one system to another. pgloader&#xA;solves this problem and turns it into a one-liner: in this talk you’ll learn&#xA;how to benefit from that, and the classic pitfalls to avoid.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Home</title>
      <link>https://pgloader.io/home/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://pgloader.io/home/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;pgloader loads data into PostgreSQL and allows you to implement&#xA;&lt;a href=&#34;https://pgloader.io/white-paper&#34;&gt;Continuous Migration&lt;/a&gt; from your current database to&#xA;PostgreSQL. Read the &lt;a href=&#34;https://pgloader.io/white-paper&#34;&gt;White Paper&lt;/a&gt; to learn how to limit&#xA;risks and control your budget, and start your PostgreSQL migration today!&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;!-- raw HTML omitted --&gt;&#xA;&lt;!-- raw HTML omitted --&gt;&#xA;&lt;p&gt;pgloader has two modes of operation. It can either load data from files,&#xA;such as CSV or Fixed-File Format; or migrate a whole database to PostgreSQL.&lt;/p&gt;</description>
    </item>
    <item>
      <title>RoadMap</title>
      <link>https://pgloader.io/roadmap/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://pgloader.io/roadmap/</guid>
      <description>&lt;p&gt;Some of the items in the pgloader Road Map will only happen given some&#xA;financial contributions to the project. You are most welcome to participate&#xA;into the progress of pgloader!&lt;/p&gt;&#xA;&lt;p&gt;The following projects are part of the pgloader Road Map, and after you&amp;rsquo;ve&#xA;bought a pgloader Moral Licence you are entitled to vote for them so see&#xA;them delivered in a time frame that makes sense for your migration projects.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Services</title>
      <link>https://pgloader.io/services/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://pgloader.io/services/</guid>
      <description>&lt;p&gt;As detailed in the &lt;a href=&#34;https://pgloader.io/white-paper&#34;&gt;Migrating to PostgreSQL White Paper&lt;/a&gt; a&#xA;database migration to PostgreSQL is set-up in the following 4 steps:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Data migration&lt;/li&gt;&#xA;&lt;li&gt;Code migration (SQL, Stored Procedure, Application Architecture, etc)&lt;/li&gt;&#xA;&lt;li&gt;Service migration (maintenance window)&lt;/li&gt;&#xA;&lt;li&gt;Opportunity cost&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;We can help you at any step above, thanks to our network of Postgres&#xA;professionals. We have collectively handled hundreds of migrations to&#xA;Postgres, taking into account many different situations, constraints, and&#xA;platforms. Whether you are migrating from MySQL or Oracle, MS SQL server or&#xA;RDS/Aurora, we can make it easier, and ensure a successful result.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Support &amp; Maintenance</title>
      <link>https://pgloader.io/support/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://pgloader.io/support/</guid>
      <description>&lt;p&gt;pgloader is open source, but running it in production is a migration project with real risk: delays, incompatibilities, and unexpected edge cases. This support offering gives you priority access, predictable maintenance, and direct influence to keep your migration and production systems under control.&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;&amp;ldquo;A migration to PostgreSQL must be approached as a project, and some risks need to be handled properly.&amp;rdquo;&#xA;&amp;ldquo;Chances are that the project will take more time than anticipated… it could even run over time and over budget.&amp;rdquo;&lt;/p&gt;</description>
    </item>
    <item>
      <title>White Paper</title>
      <link>https://pgloader.io/white-paper/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://pgloader.io/white-paper/</guid>
      <description>&lt;figure style=&#34;float: left; clear: right; display: block; width: 200px; margin-right: 1em;&#34;&gt;&#xA;    &lt;a href=&#34;https://pgloader.io/white-paper/&#34;&gt;&#xA;        &lt;img style=&#34;border: 1px solid lightblue&#34; src=&#34;https://pgloader.io/img/MigratingToPostgreSQL-Cover.png&#34;&gt;&#xA;    &lt;/a&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;p&gt;The pgloader tool is meant to allow one to implement the &lt;em&gt;&lt;strong&gt;Continuous&#xA;Migration&lt;/strong&gt;&lt;/em&gt; project methodology when migrating to PostgreSQL. This&#xA;methodology is meant to reduce risks inherent to such complex projects.&lt;/p&gt;&#xA;&lt;p&gt;After having been involved in many migration projects in the past, I decided&#xA;to publish a White Paper about this project methodology!&lt;/p&gt;&#xA;&lt;h1 id=&#34;migrating-to-postgresql-tools-and-methodology&#34;&gt;Migrating to PostgreSQL, Tools and Methodology&lt;/h1&gt;&#xA;&lt;p&gt;The migration method proposed here is called &lt;em&gt;&lt;strong&gt;Continuous Migration&lt;/strong&gt;&lt;/em&gt;.&#xA;Continuous Migration makes it easy to make incremental progress over a&#xA;period of time, and also to pause and resume the migration work later on,&#xA;should you need to do that. The method is pretty simple — just follow those&#xA;steps:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
