Babelfish: PostgreSQL with SQL Server support

PGConf.Russia 2022

June 20 – 21 |
Radisson Slavyanskaya Business Center, Square of Europe 2, Moscow

What is PGConf.Russia 2022?

About

PGConf.Russia is a leading Russian PostgreSQL international conference, annually taking together more than 700 PostgreSQL professionals from Russia and other countries — core and software developers, DBAs and IT-managers. The 2-day program includes training workshops presented by leading PostgreSQL experts, more than 40 talks, panel discussions and a lightning talk session.

i

When and Where

June 20 – 21, 2022 (10:00-19:00)
Radisson Slavyanskaya Business Center, Square of Europe 2, Moscow

Attendees

PostgreSQL DBAs
PostgreSQL core and extension developers
Application developers
System architects
IT-managers
Database migration engineers and managers.

Main topics

PostgreSQL technology frontiers for highest workloads, huge databases, mission-critical applications
PostgreSQL scalability for transactional and analytical workloads
New features in PostgreSQL and around: PostgreSQL and its ecosystem development
PostgreSQL for business software applications: system architecture, migration issues and operating experience
PostgreSQL specific features and their applications: JSON(b), (geo)Spatial data, Full text search

>500
participants

hybrid format

1000
minutes of networking

Selected talks

Ivan Chuvashov

Data Driven Lab

DBA

Talk

How to restore corrupted PostgreSQL data on your hard disc?

Every DBMS stores its data on a hard disc, so you may face a situation when your data on disc gets corrupted. This can happen due to a controller failure, logical or physical data corruption; there are also other reasons. If it is just the index file that gets corrupted, the index recreation command will enable you to restore data consistency in your DBMS. If a table file or a file of a system section gets corrupted, data restore is impossible. In this case, you need to invent workarounds. You can try to restore this data from backup files, copy it from the corrupted table, or find another way to solve this problem. In this talk, we'll tackle several cases of data corruption on disc and describe the options for restoring the data from the corrupted tables.

Slides

Vadim Yatsenko

Odin Ingram Micro

VLDB Architect

Talk

Harmful advice on autovacuum you shouldn't ever follow

PostgreSQL has a number of peculiarities that you need to take into account not only while maintaining your database but also when designing your database schema. Experienced PostgreSQL are well aware of vacuuming process. On the web one can find tons of materials covering its internals, configurations and monitoring. Many valuable talks about vacuum were given at numerous conferences. However, we still face the common wraparound problem when the maximum possible number of transactions (xid) is reached. It happens even on databases that are relatively small in size. In my presentation, I will share a customer case that looks interesting to me. A chain of mistakes made at different stages of the database's life cycle once caused a disaster. The database fully stopped for one week, we detected a wraparound and spotted corrupted blocks. Maintenance was problematical, and we spent sleepless nights in search of a solution. We managed to achieve a local win as we finally restored the database, but it's not the end of this story, which makes it even more interesting.