PGConf.Russia 2018

This talk explores the ways attackers with no authorized database access can steal Postgres passwords, see database queries and results, and even intercept database sessions and return false data. Postgres supports features to eliminate all of these threats, but administrators must understand the attack vulnerabilities to protect against them. This talk covers all known Postgres external attack methods.

In the pitch I will talk about the most important nuances of deployment and operations of the distributed analytical open-source database based on PostgreSQL - Greenplum. I will analyze the typical mistakes in its use, give the best practices and warn about bottlenecks.

I would like to share experience in runing PostgreSQL in dockerized environments, describe the specific issues and tools you will need to solve them.

• Which problems could be solved by Docker for PostgreSQL, e.g. PostgreSQLPro.9.6
• Work of IT team with Docker in development, testing and production environments
  • Using image repository and build servers for image testing
• Issues in production environment:
  • With network activity
  • With persistent repositories for Docker
  • With additional services
  • With load balancing and fail-safety
• Running PostgreSQL-base applications, such as:
  • SonarQube
  • Gitlab
  • 1С platform

Comparison of capabilities of PostgreSQL and MS SQL to work with 1С. What does pg_restore mean for 1С user? Results of load testing for 1C database of more than 1TB size. The story of one 1C Production: 2 years, 500+ databases 1C, 4TB of data, cascading replication.