title

text

February 03 – 05 , 2016

PgConf.Russia 2016

Postrelease

  • more than
    0 participants
  • 0 speakers
  • 0
    minutes of conversation
  • 60 talks
  • offline
    format

Talks

Talks archive

PgConf.Russia 2016
  • Mikhail Tyurin
    Mikhail Tyurin Avito

    My experience of working with PostgreSQL has provided clear understanding of its main advantages, making us choose and recommend choosing it.
    1. Beginning
    2. Documentation
    3. Community
    4.1 Transactional DDL
    4.2 WAL and True Physical Replication
    4.3 Transactional Snapshot and True Logical Replication and PGQ
    4.4 Exciting extensibility
    5. Success

  • Michael  Paquier
    Michael Paquier

    A backup is something that no Postgres deployments should go without as it gives the insurance to get back a deployment on its feet should a disaster strike.

    In this talk we will discuss why backups are essential in any sane PostgreSQL deployments (this seems obvious) and what are the different options available to define and set up a good backup strategy. On top of that is discussed how the future of backups would need to be handled, particularly regarding differential backups that gain in popularity among users with large deployments.

  • Ivan Panchenko
    Ivan Panchenko PostgresPro

    A year passed after birth of Postgres Pro, the Russian PostgreSQL company. The talk will describe the main achievements of the year are the future plans, including development, certification, russian documentation translate, education program.

  • Boris Veryugin
    Boris Veryugin Diasoft Platform Ltd

    Diasoft Platform company's technology solutions for migration of applications from proprietary DBMS (on the examples of Oracle and Microsoft SQL Server) to PostgreSQL will be presented in the talk. These solutions are implemented in Diasoft Database Adapter software.

    Our technology solutions allow to automate: 1) migration of database schema (including translation of stored procedure and function code); 2) migration of data; 3) migration of client applications without any change in their source code.

All talks