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 1wQCqD-001MAU-0j for pgsql-announce@arkaria.postgresql.org; Thu, 21 May 2026 23:30:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wQCq8-00BmTV-2Y for pgsql-announce@arkaria.postgresql.org; Thu, 21 May 2026 23:30:09 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wQCq7-00BmSs-2F for pgsql-announce@lists.postgresql.org; Thu, 21 May 2026 23:30:08 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wQCq6-00000000Adr-2rpK for pgsql-announce@lists.postgresql.org; Thu, 21 May 2026 23:30:07 +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=7agKS68MO0usHaMXJOrgBGrQpX/iz6A3/x5gzXoQ7kk=; b=EfvDmx0RrBaVvDW+C5owfe0G5B YD4PbHD4+dcTOerfK+/96JkU6E1MwUjZHymDbRmwP4ROYLseGRxyyINNgJmQfEzSkKe9UkrIgs88q Xa3v3m2cbGVW/y32aSrxQNN76TyPrm5FJaX2jzksmGwrzCcANuxKMcj2xETvuhFrVFyosLlPc52PV cWne+OKS9yhTDlXlqG+uMdGMyYviwEYGNV3LBTsaoEU4QN0xta/ne18kU8iaFoV3Bm920Y5PPsYi3 fbg0VJPcAugm0sENUnkk1LuRyrzlTkIVR9Ic6+AkD/Ld6HXlq1bF/lZUZ1SKhIwQ0xJCY91mhzpdY GyWIAHqA==; 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 1wQCq5-000WYK-00 for pgsql-announce@lists.postgresql.org; Thu, 21 May 2026 23:30: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 1wQCq3-004LGf-2t for pgsql-announce@lists.postgresql.org; Thu, 21 May 2026 23:30:03 +0000 Content-Type: multipart/alternative; boundary="===============3819358207239356711==" MIME-Version: 1.0 Subject: PGDay Israel 2026 - Call for Papers is Now Open To: PostgreSQL Announce From: Israel PostgreSQL Community via PostgreSQL Announce Reply-To: info@pgday.org.il Date: Thu, 21 May 2026 23:29:24 +0000 Message-ID: <177940616408.795.6089654781153695286@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: conferences X-pglister-tagsig: ca04a6023a4dd3fbd9cd357f546a486b481e9a34e3160ee15380f7bb3b47fd88 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============3819358207239356711== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Dear PostgreSQL Community, We are pleased to announce that the Call for Papers for **PGDay Israel 2026= ** is now open. We invite community members, users, and developers to submit proposals for = talks and presentations. Whether you are working with PostgreSQL in product= ion, contributing to the project, or exploring innovative use cases, we wou= ld be delighted to hear from you. **Important dates:** - Submission deadline: July 1, 2026 =20 - Speaker notifications: August 1, 2026 =20 **Submission process:** =20 Please submit your proposal(s) by email to [info@pgday.org.il](mailto:info@= pgday.org.il) Each proposal should include the following information: - Title =20 - Abstract (including any notes for the program committee) =20 - Presentation language (English or Hebrew) =20 - Speaker name(s) and affiliation(s) =20 - A short biography for each speaker =20 - Other conferences (past or future) where this proposal has been or will b= e submitted =20 - Technical requirements (internet access, video, audio, etc.) =20 - Any additional requirements =20 We look forward to your submissions and to building an engaging and high-qu= ality program together with the community. Best regards, =20 Michael Goldberg =20 On behalf of the PGDay Israel Organizing Team --===============3819358207239356711== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable PGDay Israel 2026 - Call for Papers is Now Open
 

PGDay Israel 2026 - Call for Papers is Now Open

Dear PostgreSQL Community,

We are pleased to announce that the Call fo= r Papers for PGDay Israel 2026 is now open.

We invite community members, users, and dev= elopers to submit proposals for talks and presentations. Whether you are wo= rking with PostgreSQL in production, contributing to the project, or explor= ing innovative use cases, we would be delighted to hear from you.

Important dates: - Submission deadline: July 1, 2026
- Speaker notifications: August 1, 2026

Submission process:
Please submit your proposal(s) by email to info@pgday.org.il=

Each proposal should include the following = information: - Title
- Abstract (including any notes for the program committee)
- Presentation language (English or Hebrew)
- Speaker name(s) and affiliation(s)
- A short biography for each speaker
- Other conferences (past or future) where this proposal has been or will b= e submitted
- Technical requirements (internet access, video, audio, etc.)
- Any additional requirements

We look forward to your submissions and to = building an engaging and high-quality program together with the community.<= /p>

Best regards,
Michael Goldberg
On behalf of the PGDay Israel Organizing Team
This email was sent to you from Israel PostgreSQL Community. It was deliver= ed on their behalf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to Israel PostgreSQL Community.

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