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 1wQBYp-001LFB-1C for pgsql-announce@arkaria.postgresql.org; Thu, 21 May 2026 22:08:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wQBYn-00B7ue-0t for pgsql-announce@arkaria.postgresql.org; Thu, 21 May 2026 22:08: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 1wQBYm-00B7tV-1S for pgsql-announce@lists.postgresql.org; Thu, 21 May 2026 22:08: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 1wQBYk-00000000nW4-2rad for pgsql-announce@lists.postgresql.org; Thu, 21 May 2026 22:08: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=M4uuhMUCeKrjxYsEVQPsfHAGYeTyLgIg4rwj6OxHK10=; b=7AdII2YS34UnQOohMNyM65VgR0 tL1ul6L+UdgMZe15e29aEl6JcbozKOgoH6Jbk+lTCElMpZ5dBMfmbHVe1a3fdHmTCqRkvPsXs7B/5 1vJ8CdPGwHufGhJlyNnT17jQu71xPwmnaK6EZYlWJ5qVH2ci4Y84ej61h19dGZXs0NwsvdHzbXrGm /7JZupQhZvcW0XPe8qo3urF3Y7kIqf6tSaUL8b26Cal9RGizesPN6QyfCe/Ylmlfk62Jpcdt/QaUP CpUbxzGewXpqGsLeA5eCj2CH5kErQjuIXWyPoNKqUQqQYn3n42dl4OPaiP/VMdgwnSwHGDTpQbisp xD8ZRtMg==; 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 1wQBYj-000Un1-0u for pgsql-announce@lists.postgresql.org; Thu, 21 May 2026 22:08: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 1wQBYh-004I0M-0W for pgsql-announce@lists.postgresql.org; Thu, 21 May 2026 22:08:03 +0000 Content-Type: multipart/alternative; boundary="===============3440037195560269686==" MIME-Version: 1.0 Subject: Calls for Presentations for PGConf.EU 2026 are Open To: PostgreSQL Announce From: PostgreSQL Europe via PostgreSQL Announce Reply-To: contact@pgconf.eu Date: Thu, 21 May 2026 22:08:00 +0000 Message-ID: <177940128035.799.3070638704595790905@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: conferences X-pglister-tagsig: 6bb5b508303029a7ea0e3e4dd2caa2b51270cdcc54064a567adaa76050b36e38 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============3440037195560269686== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable The Call for Papers for the PGConf.EU 2026 main conference track, as well a= s the Calls for Presentations for sessions taking place during Community Ev= ents Day, are now open. All submission deadlines close on **1 June 2026**. ## Main Conference Track The main conference CFP can be found [here](https://2026.pgconf.eu/call-for= -papers/). The conference will feature 45-minute and 25-minute sessions, all held in E= nglish. We welcome presentations on any PostgreSQL-related topic. For topic suggest= ions, please see the conference website. You can also review [last year=E2= =80=99s schedule](https://www.postgresql.eu/events/pgconfeu2025/schedule/#s= tart) for inspiration. ## Community Events Day Community Events Day will feature a number of community-led sessions and ev= ents taking place on Friday, 23 October 2026. Descriptions of the individual events and their focus areas can be found [h= ere](https://2026.pgconf.eu/community-day/). If you are interested in contributing to any of the Community Events Day se= ssions, please review the topics and submit your presentation proposal via = the submission link available on each individual event page. We look forward to welcoming another diverse range of PostgreSQL community = discussions, experiences, and ideas at PGConf.EU 2026. --===============3440037195560269686== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Calls for Presentations for PGConf.EU 2026 are Open
 

Calls for Presentations for PGConf.EU 2026 are Open

The Call for Papers for the PGConf.EU 2026 = main conference track, as well as the Calls for Presentations for sessions = taking place during Community Events Day, are now open. All submission dead= lines close on 1 June 2026.

Main Conference Track

The main conference CFP can be found here.

The conference will feature 45-minute and 2= 5-minute sessions, all held in English.

We welcome presentations on any PostgreSQL-= related topic. For topic suggestions, please see the conference website. Yo= u can also review last = year=E2=80=99s schedule for inspiration.

Community Events Day

Community Events Day will feature a number = of community-led sessions and events taking place on Friday, 23 October 202= 6.

Descriptions of the individual events and t= heir focus areas can be found here.

If you are interested in contributing to an= y of the Community Events Day sessions, please review the topics and submit= your presentation proposal via the submission link available on each indiv= idual event page.

We look forward to welcoming another divers= e range of PostgreSQL community discussions, experiences, and ideas at PGCo= nf.EU 2026.
This email was sent to you from PostgreSQL Europe. It was delivered on thei= r behalf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to PostgreSQL Europe.

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