Tips and tricks for PostgreSQL operations for 1C
As we have large 1C+PostgreSQL database setups, questions often arise, the answers to which are not so easy to find even in the documentation. I would like to share my experience in solving such issues gained during several migrations of 1C from MS SQL to PostgreSQL made for clients from the RBC500 rating. This talk will cover the following points: How in-depth your statistics should be and why it can be dangerous? How can the creation of an explicit and implicit temporary table provoke the DBMS server downtime and how can we avoid it? In what case will the DBMS process be killed by the operating system due to overuse of RAM and what to do about it? Why having one database per cluster is good and why having multiple databases on one DBMS cluster is bad? If we are stick to the "1 cluster = 1 database" approach, what about server resources for test and development environments? Backups in PostgreSQL: what backup options we have
Слайды
Дорошкевич_Тонкости_эксплуатации.pptxВидео
Видео доступно участникам мероприятия, выполнившим вход в личный кабинет
Другие доклады
-
22 мин
Anatoly Anfinogenov АО "ВНИИЖТ"Vacuum Therapy: Treatment of Chronic DB Disease
Three years ago we successfully migrated our application from Oracle DBMS to vanilla PostgreSQL. After that we faced with "childhood" diseases of our application on the new DBMS, which were successfully cured, and some "chronic diseases", which took much longer to deal with. One of the most memorable problems was the problem of DB performance degradation. The source of this problems was insufficient vacuuming of our database. The experience of understanding and solving this problem is offered to your attention in the form of practical recommendations to prevent DB tables and indices bloat and setting up PostgreSQL VACUUM/autovacuum parameters.
-
45 мин
.jpg.180x180.jpg "Dmitry Umnikov")
Dmitry Umnikov https://axenix.pro/Migrating Oracle to PostgreSQL in a high-load system with microservice architecture
A report on our experience of implementing PostgreSQL instead of Oralce in a highly loaded system with a microservice architecture that processes several terabytes of data. Let's talk about how we went from piloting Greenplum to moving to several interacting PosgreSQL databases with different load profiles, and about the problems we encountered in the process.
-
45 мин
Vladimir Lipunov ГАИШ МГУExtreme Astronomy
A popular lecture with pictures illustrating the most powerful phenomena in the Universe that put space and time in an uncomfortable position and force them to reveal the secrets of the Universe to those who have an inquisitive mind and Postgres! The story of Mr. Lipunov, professor at Moscow State University, author of world-famous popular and scientific books, theorist, experimenter and creator of a network of astronomical robots.
-
22 мин
Андрей Григорьев Ростелеком Информационные технологии.jpg.180x180.jpg "Юрий Плотников")
Юрий Плотников РТК ИТThe story on the development of a database change management solution and what we lacked in Liquibase and Flyway
We will tell you how we store database objects in the version control system. Then we compare the traditional approaches to manage database migrations and the one we preferred. We will talk about both methods advantages and disadvantages. Finally, we will present our change management solution - pgmig.