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 1w359A-000sbq-17 for pgsql-announce@arkaria.postgresql.org; Thu, 19 Mar 2026 04:38: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 1w3598-00GIvc-0o for pgsql-announce@arkaria.postgresql.org; Thu, 19 Mar 2026 04:38: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 1w3597-00GIvS-1a for pgsql-announce@lists.postgresql.org; Thu, 19 Mar 2026 04:38: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 1w3593-000000013qv-3SkR for pgsql-announce@lists.postgresql.org; Thu, 19 Mar 2026 04:38: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=4eb1AYLTFD6/Whmlz8dnIH9JrU9U06TUKQsRWF3ZpTQ=; b=t3zcLWcA6+PhFBNqeFHt/Q+XVj xiMvKphMl8FnZLlUjPSkdxmZ+XMHlpbyghcw8JJ9sqwMXzdDH4oSEVe0qgDDg+30XAup428KZGhbj yEne0bTbPbw/hNdRxQ0am0KG1CYWSREHzfudVAPgpvp7Y5TZsmqll4KXt2WQ6uYprIMHdJhpbm7/9 FC3cfn6mi57NRQmx9W3CVcAmpUsLUekP8t7Zmaj+TTpBzlPEp1TxLik6EMPWAgIJPN2nwyUjNl2vX 4g1Yq/IDlyGSEMHYOZ46J2c9jdKxundFZ33BggKoHKutrSDpg5M7GRNqB0x/O5OdTje1G10fU12fI JkRmwAfA==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w3592-001JtX-1O for pgsql-announce@lists.postgresql.org; Thu, 19 Mar 2026 04:38: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 1w3590-004V2B-2g for pgsql-announce@lists.postgresql.org; Thu, 19 Mar 2026 04:38:02 +0000 Content-Type: multipart/alternative; boundary="===============3292679637968241111==" MIME-Version: 1.0 Subject: PGConf.dev 2026 Schedule Announced! To: PostgreSQL Announce From: Slonik Events Canada via PostgreSQL Announce Reply-To: contact@pgconf.dev Date: Thu, 19 Mar 2026 04:37:29 +0000 Message-ID: <177389504953.809.15334131174550128853@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: conferences X-pglister-tagsig: 482179ef1b962f2081420194a47b45699004f7acce8f413f2f88ce9d5f0526d0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============3292679637968241111== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [PGConf.dev 2026](https://2026.pgconf.dev/) (May 19-22, 2026, Vancouver, BC= , Canada), aka [PostgreSQL Development Conference 2026](https://2026.pgconf= .dev/), is an event where users, developers, and community organizers come = together to focus on PostgreSQL development and community growth. Meet [Pos= tgreSQL](https://www.postgresql.org) contributors, learn about upcoming fea= tures, and discuss development problems with PostgreSQL enthusiasts! We're thrilled to announce the [PGConf.dev 2026 schedule](https://2026.pgco= nf.dev/schedule)! This year, PGConf.dev expanded the program to include com= munity-led sessions on Tuesday! We also have some special events and talks = planned around the 30th Anniversary of the PostgreSQL project! You can find= details of the schedule at the URLs below, including talks and sessions th= at highlight PostgreSQL development and community growth, and stories from = users, developers and community organizers: * Tuesday, May 19: [https://2026.pgconf.dev/schedule/tuesday](https://2026.= pgconf.dev/schedule/tuesday) * Wednesday, May 20: [https://2026.pgconf.dev/schedule/wednesday](https://2= 026.pgconf.dev/schedule/wednesday) * Thursday, May 21: [https://2026.pgconf.dev/schedule/thursday](https://202= 6.pgconf.dev/schedule/thursday) * Friday, May 22: [https://2026.pgconf.dev/schedule/friday](https://2026.pg= conf.dev/schedule/friday) [Registration](https://2026.pgconf.dev/attend) is currently open - be sure = to register soon to guarantee your spot! If you're traveling to Vancouver, we recommend you [book your accommodation= s soon](https://2026.pgconf.dev/attend/travel). We've included a travel and= accommodations guide here: [https://2026.pgconf.dev/attend/travel](https://2026.pgconf.dev/attend/trav= el) [PGConf.dev 2026](https://2026.pgconf.dev/) is made possible with the [gene= rous support of our sponsors](https://2026.pgconf.dev/sponsor). PGConf.dev = is the premier worldwide gathering of PostgreSQL contributors, and is a cha= nce to collaborate on upcoming PostgreSQL development. Your sponsorship hel= ps directly with the ongoing development of PostgreSQL. To find out more ab= out [sponsorship opportunities](https://2026.pgconf.dev/sponsor/levels), pl= ease visit the [sponsorship page](https://2026.pgconf.dev/sponsor/levels), = or contact us at [sponsors@pgconf.dev](mailto:sponsors@pgconf.dev): [https://2026.pgconf.dev/sponsor/levels](https://2026.pgconf.dev/sponsor/le= vels) We look forward to seeing you in Vancouver in May! --===============3292679637968241111== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable PGConf.dev 2026 Schedule Announced!
 

PGConf.dev 2026 Schedule Announced!

PGConf.dev 2026 (May 19= -22, 2026, Vancouver, BC, Canada), aka PostgreSQL Developmen= t Conference 2026, is an event where users, developers, and community o= rganizers come together to focus on PostgreSQL development and community gr= owth. Meet PostgreSQL contributors, learn about upcomi= ng features, and discuss development problems with PostgreSQL enthusiasts!<= /p>

We're thrilled to announce the PGConf.dev 2026 schedule! This year, PGConf.dev expanded the= program to include community-led sessions on Tuesday! We also have some sp= ecial events and talks planned around the 30th Anniversary of the PostgreSQ= L project! You can find details of the schedule at the URLs below, includin= g talks and sessions that highlight PostgreSQL development and community gr= owth, and stories from users, developers and community organizers:

Registration is cu= rrently open - be sure to register soon to guarantee your spot!

If you're traveling to Vancouver, we recomm= end you book your accommodations soon. We'v= e included a travel and accommodations guide here:

https://2026.pg= conf.dev/attend/travel

PGConf.dev 2026 is made= possible with the generous support of our sponsors. PGConf.dev is the premier worldwide gathering of PostgreSQL contributor= s, and is a chance to collaborate on upcoming PostgreSQL development. Your = sponsorship helps directly with the ongoing development of PostgreSQL. To f= ind out more about sponsorship opportunities, please visit the sponsorship page, or = contact us at sponsors@pgconf.dev:

https://2026.p= gconf.dev/sponsor/levels

We look forward to seeing you in Vancouver = in May!
This email was sent to you from Slonik Events Canada. It was delivered on t= heir behalf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to Slonik Events Canada.

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/.
 
--===============3292679637968241111==--