PgConf.Russia 2017

< 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.

Full text search in PostgreSQL is probably the most advanced one among relational DBMS. This tutorial will explain how to setup full text search configurations and dictionaries and how to build a ful text search system using an example of a simple popular science web site, with demonstration of various ranking functions. Also I will tell about new RUM index, which allows to accelerate execution of some kinds of full text queries and implements a new improved ranking function.

I want to present a new custom access method, which extends the current GIN capabilities using additional information stored in posting tree/list. For example, positional information as an additional information allows new AM returns results in relevance order, which could considerably improve execution time of full text queries.

This talk is about migrating an electronic document management system from MS SQL to PostgreSQL 9.5 or higher as part of the import phaseout initiative. We will touch upon architecture specifics, as well as describe the problems we encountered when migrating T-SQL code to pgsql, and how we resolved them.

Learn more at https://pgconf.ru/news/94168

VIDEO