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.94.2) (envelope-from ) id 1v1V64-009ItA-NN for pgsql-announce@arkaria.postgresql.org; Wed, 24 Sep 2025 19:24:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1v1V63-00FCoZ-Cl for pgsql-announce@arkaria.postgresql.org; Wed, 24 Sep 2025 19:24:11 +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.94.2) (envelope-from ) id 1v1V62-00FCoM-Ic for pgsql-announce@lists.postgresql.org; Wed, 24 Sep 2025 19:24:10 +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.96) (envelope-from ) id 1v1V5y-002gHw-0i for pgsql-announce@lists.postgresql.org; Wed, 24 Sep 2025 19:24:10 +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=h9kKXvjZ7SuxF17SnguabjWAlBJvS2IzFmHoprgbgwo=; b=2jwSZqeiFy2Sh3fKa1k5PmumhG gRxWVO/TYOufV4hPpqzlWQ0tvIaGGBheBdyf8o7n5cy+XPuC+PLCOWSwi9yf4hKon+BDPyLFJpWsU wCJZIwRgfjicx99XkWkETIe0H7juQbBtI6FkXvXncUyt+Rahw1g+naZ1HbSyCew4TF5BM2HZPQ+xr XoSMa4KJLd0d6DqTFfoiCX7rj2buyiXC1VK3/NMgsocVjGmPBr/0y3or4XylImD4UBzOK0FPr04wt vQZeV0BY4LuftykUKWW0/WbWc6Ycj+eQb9liLLu2x+GCC6NWKuzknTI5JxixYoZHFYm4Q2ccUQAcO Idklh6NA==; 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.94.2) (envelope-from ) id 1v1V5y-005niq-4s for pgsql-announce@lists.postgresql.org; Wed, 24 Sep 2025 19:24:06 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1v1V5v-00AhN8-1J for pgsql-announce@lists.postgresql.org; Wed, 24 Sep 2025 19:24:03 +0000 Content-Type: multipart/mixed; boundary="===============7001836666897738353==" MIME-Version: 1.0 Subject: PGConf.dev 2026 Call for Proposals is Open To: PostgreSQL Announce From: Slonik Events Canada via PostgreSQL Announce Reply-To: contact@pgconf.dev Date: Wed, 24 Sep 2025 19:23:34 +0000 Message-ID: <175874181453.853.17556896966088654749@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: conferences X-pglister-tagsig: 0b21c94b140a9174dea5b4762f48bbdb1027bdd45dca9f249b97c0a49c71f9aa List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============7001836666897738353== Content-Type: multipart/alternative; boundary="===============7902669492785224983==" MIME-Version: 1.0 --===============7902669492785224983== 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, CA= ), 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 [PostgreSQL]= (https://www.postgresql.org) contributors, learn about upcoming features, a= nd discuss development problems with PostgreSQL enthusiasts! The [call for proposals](https://2026.pgconf.dev/cfp) is open through Janua= ry 16, 2026! We're looking for presentations, workshops, and other content = focused on PostgreSQL development: new PostgreSQL features and initiatives,= community process improvements, lessons from other open source communities= , and more! A full list of ideas is available on the [CFP](https://2026.pgc= onf.dev/cfp) page: This year we have a new content type in the CFP, [Community Discussion Sess= ions](https://2026.pgconf.dev/cfp#organize), which are interactive sessions= where you can discuss ideas for PostgreSQL development and community in a = meeting format. Even if you've never presented at a PostgreSQL event before, [we'd love to = hear your ideas](mailto:program@pgconf.dev) and can provide feedback on you= r proposal! You can submit your content proposals here: [https://2026.pgconf.dev/cfp](https://2026.pgconf.dev/cfp) [PGConf.dev 2026](https://2026.pgconf.dev/) is not possible without the [ge= nerous support of our sponsors](https://2026.pgconf.dev/sponsor-levels). PG= Conf.dev is the premier worldwide gathering of PostgreSQL contributors, and= is a chance to collaborate on upcoming PostgreSQL development. Your sponso= rship helps directly with the ongoing development of PostgreSQL. To find ou= t more about [sponsorship opportunities](https://2026.pgconf.dev/sponsor-le= vels), please 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! --===============7902669492785224983== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable PGConf.dev 2026 Call for Proposals is Open
 

PGConf.dev 2026 Call for Proposals is Open

PGConf.dev 2026 (May 19= -22, 2026, Vancouver, CA), aka PostgreSQL Development Conf= erence 2026, is an event where users, developers, and community organiz= ers come together to focus on PostgreSQL development and community growth. = Meet PostgreSQL contributors, learn about upcoming fea= tures, and discuss development problems with PostgreSQL enthusiasts!

The call for proposals is open through January 16, 2026! We're looking for presentations, worksh= ops, and other content focused on PostgreSQL development: new PostgreSQL fe= atures and initiatives, community process improvements, lessons from other = open source communities, and more! A full list of ideas is available on the= CFP page:

This year we have a new content type in the= CFP, Community Discussion Sessions, which a= re interactive sessions where you can discuss ideas for PostgreSQL developm= ent and community in a meeting format.

Even if you've never presented at a Postgre= SQL event before, we'd love to hear your ideas and can = provide feedback on your proposal!

You can submit your content proposals here:=

https://2026.pgconf.dev/c= fp

PGConf.dev 2026 is not = possible without the generous support of our s= ponsors. PGConf.dev is the premier worldwide gathering of PostgreSQL co= ntributors, and is a chance to collaborate on upcoming PostgreSQL developme= nt. Your sponsorship helps directly with the ongoing development of Postgre= SQL. To find out more about sponsorship opport= unities, 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/.
 
--===============7902669492785224983==-- --===============7001836666897738353==--