--- title: "PGConf India 2026" description: "Sharing experience and learnings about my first profession conference." author: "Samba Siva" published: 2026-03-16T17:00:37.720Z updated: 2026-11-06T16:22:34.627Z tags: - "PostgreSQL" - "Conference" url: "https://sambasivareddy.in/blog/pgconf-india-2026" --- # PGConf India 2026 > Between: 12 March - 13 March This was **_my first ever professional conference_** to attend. I was very excited for this, ever since my manager asked whether I wanted to go or not, since it helps me understanding how the community members/developers think and approach about the **Postgres**. And moreover, it would help me to gain knowledge and how fellow developers are gaining more insights about Postgres. * * * ## Talks I attended ### A Deep Dive into SSL: Serializable Snapshot Isolation in Postgres > By Vaijayanthi Bharadwaj (EDB) In this talk, the speaker explained how Serializable transactions work internally in PostgreSQL. When a two concurrent transactions executed with Serializable Isolation, we can assume that the both transactions are executed in serial manner i.e one after the another. **_Main Points:_** 1. Serializable Dependency Graph 1. RW Edge 2. WW Edge 3. WR Edge 2. Strict Two-phase Locking (S2PL): Algorithm to implement Serializability. 3. Serializable Xact: Per Transaction SSI State ### Case Study: Understanding the importance of CommitLog through a Database corruption > By Amit Kumar Singh (EDB) This talk was about how we can debug/understand a Database corruption issue using a commit log. And the speaker talks about his experience in debugging the core issue using various extensions and **how important is to always upgrade your Postgres system whenever a minor version available.** Extension Discussed: 1. pg\_inspect: Helps us to inspect the pages. 1. Can also helps to get tuple headers which can be helpful in identifying the corrupted tuples. 2. Tuple Headers: 1. _HEAP\_XMAX\_INVALID_ 2. _HEAP\_XMIN\_COMMITTED_ 3. _HEAP\_XMAX\_INVALID_ 4. _HEAP\_XMIN\_INVALID_ 5. _HEAP\_XMAX\_INVALID_ 2. amcheck: To find the corrupted tables. 3. pg\_surgery: provides various functions to perform a surgery on a relation like: 1. Marking a tuple dead with the help of heap\_force\_kill() 2. Marking a tuple freezed with the help of heap\_force\_freeze() 4. catcheck 5. pg\_visibility ### Ten Postgres Hacker Journey - and what they teach us > By Claire Giordano (Microsoft) This talk was about top ten postgres hackers/committers/contributors and how they motivate themselves to code and contribute to Postgres Open Source. Main Points: 1. Postgres Talking: A podcast hosted by the speaker. It can helps to any individual working on postgres whether they can be App Developer, DBA, Data Engineer, Contributors etc. 2. What are main 4 forces that shaped these hackers 1. Catalysts - How, Why, When? 2. Knowledge Inputs 3. Invisible Curriculum 4. Learning through Code. ### pg\_search: Bringing Elasticsearch-grade search to PostgreSQL > By Mithun C Yogendra (ParadeDB) This talk was about the pg\_search extension built for the postgres using Rust. Main Points: 1. Scoring by BM25 Algorithm 2. Types of Indexes: 1. Inverted Index: Full-Text Search 2. Columnar Index: Agg, Filters etc.. 3. What have built on top of postgres 1. Custom BM25 Index 2. Custom FTS Operators (|||, &&&, ===, ###) 3. Query Builder which converts FTS operations to PG understandable. ### Where is my Memory? > By Phuskar Khadilkar, Mohit Agarwal (Google) This talk was about how we can identify a potential memory leaks in postgres/postgres extension. And sometimes, how memory leaks can happen beyond the postgres that is memory leaks that postgres cannot identify by itself. Main Points: 1. Explained how the memory allocated in shared buffers and how it store in OS and RAM. 2. Extensions: 1. pg\_buffercache 2. pg\_shmem\_allocations 3. Tools: 1. memleak-bpfcc 2. flamegraph For this talk, speaker injected a memory leak in the postgres by using mmap in a postgres extension. mmap is controlled by postgres so it don't have any idea about the memory allocated by it. ### Understanding Locking and Concurrency in Postgres > By Pavan Deolasse (EDB) This talks was about how the locking and concurrency works in Postgres. Speaker also talked about what locking provides, what problems we can face without locking, types of locks etc. Main Points 1. Types of Locks 1. Spinlocks 2. LWLocks 3. HeavyWeight Locks 2. pg\_locks extension 3. Lockable Objects 1. Relation 2. Tuple 3. Transaction ID 4. Extend 5. Object 6. Advisory 4. Lock Lifecycle 5. Table/Row Level Locks 6. Lock Manager Data structure 7. Some important things: 1. REINDEX Concurrently 2. DROP INDEX concurrently 3. NOT VALID constraint 4. Always setting lock\_timeout before DDLs ### End of Analyze Hell (Postgres 18) > By Rajkumar Raghuwanshi, Nishad Mankar (AWS) This talk was about how pg\_upgrade works in older PG versions compared to newer 18 version. Main Points: 1. In older version, pg\_upgrade will do the following things: 1. Copy Schema 2. Links/Copies Data files 3. Faster Upgrade 2. But it won't do transferring optimizer statistics, causing the queries in new upgraded system behaving differently then how they executed in older versions. 1. So we have to manually to ANALYZE or VACUUM to update the stats so that queries will be executed better. 3. From PG 18+ onwards, pg\_upgrade will take care of transferring the optimizer stats as well there by removing one extra hop for the developers/DBAs. * * * ## Fun Initially I thought, the conference is always about networking, professional talks, technical discussions etc.. but in this conference there were also the quizzes conducted by the various companies. You may ask you said fun, but talking about the quizzes, but it is like technical fun. Participated in every company's quizzes, won some, lost on last question for some, thrashed in some. But it was so amazing to see so many talented people and felt happy to compete against them. * * * Looking forward for the next year's PGConf!!