# PostgreSQL FOSDEM 2015

DevFeed: [PostgreSQL FOSDEM 2015](<https://devfeed.tech/articles/postgresql-fosdem-2015-34659.md>)

Original publisher: [Read original article](<https://tapoueh.org/conf/postgresql-fosdem-2015/>)

Published: 2015-01-30T23:00:00Z

Content type: article

Language: en

Sources: [Dimitri Fontaine](<https://devfeed.tech/sources/dimitri-fontaine.md>)

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [FOSDEM](<https://devfeed.tech/topics/fosdem.md>), [backups](<https://devfeed.tech/topics/backups.md>), [MySQL](<https://devfeed.tech/topics/mysql.md>)

Tags: [backups](<https://devfeed.tech/tags/backups.md>), [fosdem](<https://devfeed.tech/tags/fosdem.md>), [migrate](<https://devfeed.tech/tags/migrate.md>), [mysql](<https://devfeed.tech/tags/mysql.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>)

## AI overview

A FOSDEM 2015 post highlights talks about automated data restoration and migrating a full MySQL database to PostgreSQL with pgloader using a single command line.

## Source excerpt

Backups are not interesting. Don't make backups. Instead, set-up an all automatic data restoring facility, that you can use in nightly scripts or interactively, when the worst happens. The first talk is about what happens when you're merely doing backups and the worst happens. The second talk is about pgloader and how to migrate a full MySQL database to PostgreSQL using a single command line!