Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vpi9Q-00E5aN-0v for pgsql-announce@arkaria.postgresql.org; Tue, 10 Feb 2026 07:27:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vpi9O-00EF4i-36 for pgsql-announce@arkaria.postgresql.org; Tue, 10 Feb 2026 07:27:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vpi9O-00EF4T-0Q for pgsql-announce@lists.postgresql.org; Tue, 10 Feb 2026 07:27:09 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vpi9L-00000001x07-0Ehz for pgsql-announce@lists.postgresql.org; Tue, 10 Feb 2026 07:27:09 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:From:To:Subject: MIME-Version:Content-Type:Sender:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:In-Reply-To:References; bh=WIRY9eRE+ptZkI1pgoBPx8PES0Rv7uQCrK9Lmg3/TT0=; b=GAXSmBzJdCnssOd9K8LBaglQg+ 18SvrWBKjGt8RpryQM/UtFQefYdGb1pQEXc7nnXOcpq/aCIJ91VUvSKdP0IxQ0mItWtfgRKS4j3bd XcYgXWJ1ZOmJqAcIO3Pk2Qj0wqTxwkHYAGD4beIeA6dB6eRzVoi2LQldv+bL1vR/x+nr/RFl5uuUw A+VsXPFrDyU8WCBX7gykw4p9651cGaJdeSuziPS/dY4VIK19/ynPIjVMtCIsLURCP5piEsELD5Kx3 Z3/GqK/5Sdmc8a+ghasM9NrMkQg30gC/e3Yzlrzl/4FBKvW8XC9LZRGPsABxTzQ8eavclWscsJQcm AzWcMfhg==; Received: from wrigleys.postgresql.org ([217.196.149.60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vpi9J-005h8p-0M for pgsql-announce@lists.postgresql.org; Tue, 10 Feb 2026 07:27:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vpi9G-007Bzr-1M for pgsql-announce@lists.postgresql.org; Tue, 10 Feb 2026 07:27:02 +0000 Content-Type: multipart/alternative; boundary="===============8146636651011312227==" MIME-Version: 1.0 Subject: =?utf-8?q?PGDay_Bangkok_2026_at_FOSSASIA_Summit_=E2=80=93_Schedule_Now_Published?= To: PostgreSQL Announce From: FOSSASIA via PostgreSQL Announce Reply-To: office@fossasia.org Date: Tue, 10 Feb 2026 07:26:23 +0000 Message-ID: <177070838303.790.7310183779364970497@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: conferences X-pglister-tagsig: 7677801e50f703831de0c380070c9dbaea9cb4e791e08000a60d9333bbfe9099 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============8146636651011312227== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable The schedule for [**FOSSASIA PGDay 2026**](https://eventyay.com/e/b85fd0f2/= schedule ) is now published. The event will take place on **March 10, 2026**, at **T= rue Digital Park** in **Bangkok**, Thailand. The Programme Committee has curated a one-day programme covering core devel= opment, performance and indexing, high availability and disaster recovery, = backups, security, and operational practices. The day will also include tim= e for discussion and informal networking with speakers and community member= s. The programme includes **two keynotes** on **software longevity through 30 = years of PostgreSQL** and **PostgreSQL=E2=80=99s community and contribution= model**, alongside in-depth technical sessions on topics such as PostgreSQ= L catalogs and metadata introspection, indexing evolution, wildcard search = performance, logical vs. physical backups, authentication and security enfo= rcement, HA vs. DR in production, and operational challenges such as on-cal= l practices. Attendees will also get a look at extensions and PostgreSQL in= ternals work, including **pg_ivm**, **pg_fusion**, and **Biscuit**, as well= as a hands-on session with **PostgreSQL 18 demos**. **Register here:** [summit.fossasia.org/pgday](https://summit.fossasia.org/= pgday) We look forward to welcoming the PostgreSQL community to Bangkok on **March= 10, 2026**. --===============8146636651011312227== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable PGDay Bangkok 2026 at FOSSASIA Summit =E2=80=93 Schedule Now Pub= lished
 

PGDay Bangkok 2026 at FOSSASIA Summit =E2=80=93 Schedule Now Publishe= d

The schedule for FOSSASIA PGDay 2026 is now published. The event w= ill take place on March 10, 2026, at True Digital = Park in Bangkok, Thailand.

The Programme Committee has curated a one-d= ay programme covering core development, performance and indexing, high avai= lability and disaster recovery, backups, security, and operational practice= s. The day will also include time for discussion and informal networking wi= th speakers and community members.

The programme includes two keynotes= on software longevity through 30 years of PostgreSQL and PostgreSQL=E2=80=99s community and contribution model, alongside in-depth technical sessions on topics such as PostgreSQL ca= talogs and metadata introspection, indexing evolution, wildcard search perf= ormance, logical vs. physical backups, authentication and security enforcem= ent, HA vs. DR in production, and operational challenges such as on-call pr= actices. Attendees will also get a look at extensions and PostgreSQL intern= als work, including pg_ivm, pg_fusion, an= d Biscuit, as well as a hands-on session with Post= greSQL 18 demos.

Register here: summit.fossasia.org/pgday

We look forward to welcoming the PostgreSQL= community to Bangkok on March 10, 2026.
This email was sent to you from FOSSASIA. It was delivered on their behalf = by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to FOSSASIA.

You were sent this email as a subscriber of the pgsql-announce mai= linglist, for the content tag Community Conferences. To unsubscribe from further emails, or change which emails you want to receive, please click th= e personal unsubscribe link that you can find in the headers of this email, or visit https://lists.postgresql.org/unsubscribe/.
 
--===============8146636651011312227==--