PgConf.Russia 2017

Do you test your PostgreSQL releases prior to Production in a dedicated test environment? Are you sure that your test environment (shortly Test) is equal to Production and in an appropriate state?

In Skype we were facing multiple challenges associated with database testing:
- Simplifying complex Production architecture of thousands of PostgreSQL instances, interconnected with RPCs and replications, infrastructure servers and external DB scripts, into their Test counterparts.
- Constantly growing hardware requirements, insufficient cleanup of data generated in Test.
- Differences between Test and Production were appearing and accumulating. Recognizing and fixing them required lots of effort.

1. Why is it time to consider switching to PostgreSQL?
2. 1С and PostgreSQL interoperability.
3. Why should we start with Windows?
4. The first experience of migrating big enough 1С databases to Postgres.
5. Large-scale projects on high-load systems, in figures.

The new ISO/IEC 9075-2:2016 standard specifies JSON data and operations syntax and semantics specifics for SQL. This talk overviews the requirements of this standard, and focuses on the differences between them and the actual implementation of JSON/JSONB in PostgreSQL. Special attention will be paid to JSON Path (XPath analogue), SQL/JSON functions and our plans to make Postgres compliant with this standard.

VIDEO

It often happens that you already have PosgtreSQL in production, but you don’t have a DBA. To demystify the PostgreSQL database, I’ll tell you how to troubleshoot various problems while working with PosgtreSQL. We will try to understand how to answer "routine" questions of a typical system administrator: - Is everything OK with the database? - What consumes DB server resources? - What to optimize first to reduce resource consumption?

VIDEO