PgConf.Russia 2019

Magic tricks followed by exposure (1C+PG):

• Focus number one. How to convince the accounting department to buy a new server.
• Focus number two. How to show that MS SQL is faster than PostgreSQL.
• Focus number three. How to show that PostgreSQL is faster than MS SQL Server.

It's so good when database behaves predictable. When the performance is lacking, you just add CPU cores, terabytes of RAM and millions of IOPS, and everything becomes good again. But it's rather unpleasant, when server have plenty of free resources, while database is still running slow. And it's especially sad if stress testing detects no problems, while real life workload of the same volume makes your database hang.

In this talk I will consider bottlenecks of PostgreSQL, which we met in our practice, and which causes sad behavior described above. I'll also explain what can be done at user level in order to evade these bottlenecks, and what developers are planning to do in order to eliminate those bottlenecks. I'm also planning give some recipes of stress testing, which could have to evade surprises in production.

To migrate to a PostgreSQL/Postgres Pro we need multi-core servers to be carefully tuned for correct parallelism. What settings make multi-terabyte installations work fast and correctly?

We will share our PostgreSQL/Postgres Pro on BullSequana S and Bullion S servers testing experience.

The features of this hardware platform which are crucial for high-loaded configurations
• Multi-core Scale-up servers and PostgreSQL/Postgres Pro
• Results of stress testing of PostgreSQL/Postgres Pro running on the equipment.

Meeting corporate standarts for information security, business continuity and software unification: Kerberos Authentification (Windows and Linux) in Active Directory Environment. 1C Enterprise specifics. Using backup and recovery software (HP Data Protector). Integration with corporate monitoring system (Solarwinds Mointor).