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 1s1iRq-00EJUA-Mx for pgsql-announce@arkaria.postgresql.org; Tue, 30 Apr 2024 08:02:46 +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 1s1iRo-0052JB-9F for pgsql-announce@arkaria.postgresql.org; Tue, 30 Apr 2024 08:02:45 +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 1s1iNO-004d9q-DS for pgsql-announce@lists.postgresql.org; Tue, 30 Apr 2024 07:58:11 +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.94.2) (envelope-from ) id 1s1iNL-000oVE-P7 for pgsql-announce@lists.postgresql.org; Tue, 30 Apr 2024 07:58: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=legSxWALQ3Z237u/sfRZwS7N1GfN+BDsD+CHbD4sNHU=; b=QJ628rSKuggIAi53U1tFqbWJn/ OZKqZdqpZF8Ty3za5NfgqRxb+jDD3q1c+IMK1Z9RuRbu6R6e50KgD0AK1jIHdoOhiilHPgCDEFxia knyqacD1WLK73nMBa89+40sq36b89+JfC0I4fcH6UCWDq3JSvOx3EhFRXQG3gU6lGJjbdE95tNFZX YtsDN3SI5tdCKOG3ETYgiypoMCbMz8mjE4giNPMSSnwct+3fUqGkOZTQ3YQ2wVXu0NUYwt9SsrVoG YrDt4MejBBJfNAlaK1lIgcmcQpqFPvwtfl1tuGxrNRT19liy5igxWAgRyZQn1UW23+1KZJKqtdveF Wkr1Nqpg==; 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 1s1iNJ-002MIe-GS for pgsql-announce@lists.postgresql.org; Tue, 30 Apr 2024 07:58:06 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1s1iNG-006rO5-4R for pgsql-announce@lists.postgresql.org; Tue, 30 Apr 2024 07:58:03 +0000 Content-Type: multipart/mixed; boundary="===============0414059645518562914==" MIME-Version: 1.0 Subject: PGConf.dev 2024 - Registration selling out - please register ASAP! To: PostgreSQL Announce From: Slonik Events Canada via PostgreSQL Announce Reply-To: contact@pgconf.dev Date: Tue, 30 Apr 2024 07:57:43 +0000 Message-ID: <171446386378.705.12990593490127915926@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: conferences X-pglister-tagsig: 24bb64970f8e2a432953b79ccb211aae3bffdf4490d9aa7a622a8d9ab78269ea List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============0414059645518562914== Content-Type: multipart/alternative; boundary="===============0213360945561508954==" MIME-Version: 1.0 --===============0213360945561508954== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [PostgreSQL Development Conference 2024](https://2024.pgconf.dev/) ([PGConf= .dev 2024](https://2024.pgconf.dev/)) (May 28, 2024 - May 31, 2024; Vancouv= er, Canada) is where users, developers, and community organizers come toget= her to focus on PostgreSQL development and community growth. Meet PostgreSQ= L contributors, learn about upcoming features, and discuss development prob= lems with PostgreSQL enthusiasts! Given the overwhelming support from the [PostgreSQL](https://www.postgresql= .org) community, we're already almost at the capacity of our venue for this= year and are close to selling out. If you have not already [registered for= PGConf.dev 2024](https://2024.pgconf.dev/registration/), please do so toda= y: [https://2024.pgconf.dev/registration/](https://2024.pgconf.dev/registratio= n/) Once we have reached our registration capacity, we will open up a first-com= e, first-serve waitlist. We're thrilled to have a wonderful lineup of talks that highlight topics on= PostgreSQL development and community growth, featuring stories from users,= developers, and community organizers. You can find out more about the [PGC= onf.dev 2024 schedule](https://www.pgevents.ca/events/pgconfdev2024/schedul= e/) here: [https://www.pgevents.ca/events/pgconfdev2024/schedule/](https://www.pgeven= ts.ca/events/pgconfdev2024/schedule/) PGConf.dev 2024 is not possible without the generous support of our [sponso= rs](https://2024.pgconf.dev/sponsors/). Sponsorship helps us bring together= the worldwide PostgreSQL community to focus on upcoming development and co= mmunity building topics. You can find out more about [sponsorship opportun= ities](https://2024.pgconf.dev/sponsor-levels/) here: [https://2024.pgconf.dev/sponsor-levels/](https://2024.pgconf.dev/sponsor-l= evels/) We look forward to seeing you in Vancouver in May! --===============0213360945561508954== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable PGConf.dev 2024 - Registration selling out - please register ASA= P!
 

PGConf.dev 2024 - Registration selling out - please register ASAP!

PostgreSQL Development Conf= erence 2024 (PGConf.dev 2024) (May 28, 2024 - May 31= , 2024; Vancouver, Canada) is where users, developers, and community organi= zers come together to focus on PostgreSQL development and community growth.= Meet PostgreSQL contributors, learn about upcoming features, and discuss d= evelopment problems with PostgreSQL enthusiasts!

Given the overwhelming support from the PostgreSQL community, we're already almost at the capacit= y of our venue for this year and are close to selling out. If you have not = already registered for PGConf.dev 2024, ple= ase do so today:

https://2024.pg= conf.dev/registration/

Once we have reached our registration capac= ity, we will open up a first-come, first-serve waitlist.

We're thrilled to have a wonderful lineup o= f talks that highlight topics on PostgreSQL development and community growt= h, featuring stories from users, developers, and community organizers. You = can find out more about the PG= Conf.dev 2024 schedule here:

PGConf.dev 2024 is not possible without the= generous support of our sponsors. Sponsorship = helps us bring together the worldwide PostgreSQL community to focus on upco= ming development and community building topics. You can find out more abou= t sponsorship opportunities here:

https://2024.= pgconf.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/.
 
--===============0213360945561508954==-- --===============0414059645518562914==--