PgConf.Russia 2017

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

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.

< Query failed: ERROR: deadlock detected
< DETAIL: Process 17371 waits for ShareLock on transaction 102733872; Blocked by process.
< Process 10414 waits for ShareLock on transaction 102733874; Blocked by process 17371.

Such "unpleasant" messages from the server can seriously puzzle the developer. When working with locks, in particular, with transactions in general, it is necessary to take into account the features of the implementation of client libraries, which can cause the above exception.

In the short talk, the mechanics of the interaction of locks will be explained, main attention being paid to causes of deadlocks. References to the relevant documentation pages will be given. A technique of "bypassing" this problem of concurrent data access will be described and illustrated with some generalized examples from practice are shown. The talk will be interesting to database developers and administrators as well as the client-side application developers.

It's not a secret that PostgreSQL connections are expensive so you should save them. To solve this problem there are PgPool-II and PgBouncer for quite a long time. At Yandex tens of thousands of connections to a single database is not a surprise so we use pgbouncer since time immemorial. This talk gives an overview of problems we faced and ways to solve them.

VIDEO