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 1urDSo-002RDk-BX for pgsql-announce@arkaria.postgresql.org; Wed, 27 Aug 2025 10:33:12 +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 1urDSn-00E8jK-I3 for pgsql-announce@arkaria.postgresql.org; Wed, 27 Aug 2025 10:33:10 +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.94.2) (envelope-from ) id 1urDSm-00E8iR-FC for pgsql-announce@lists.postgresql.org; Wed, 27 Aug 2025 10:33:09 +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.96) (envelope-from ) id 1urDSj-00205H-2X for pgsql-announce@lists.postgresql.org; Wed, 27 Aug 2025 10:33:08 +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=c/RbWCn9wp3bQhOwEHz0/oofrnfcLdfiB1PqYebBbyI=; b=rX/obEngRaOLJRXqbfo+4kX2gY Uo3eWjNTTkOX1+enCSgLyXyD/AwgTJo3gcgYBtfG/61trV6pdWq9f7dhnYKGEVvJQh5bMQlSSLMrs e8D0n12PJcCWfWziH1EketnOTOyveou9eQ9dPcGW1TPjb8QN+h1naqv8FWKN7FsA6kR+eqKk2Y0SU NOZRolBrJjHEnuwxVqlLi4xScr0tj4nJJ6BssesRV9tH8q4sh2XIW532eHbLGKufBQ65G4loKEdgy h3chaQU9EoOkpdTDRe56fUywuGmRW1hgPFGdPHdSW3YT6o1Dphr+PDudOce5+BWR95Njtkb5OPtLL nqVgFQ4w==; 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 1urDSj-005Vkz-Lv for pgsql-announce@lists.postgresql.org; Wed, 27 Aug 2025 10:33: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 1urDSh-00Behz-0v for pgsql-announce@lists.postgresql.org; Wed, 27 Aug 2025 10:33:03 +0000 Content-Type: multipart/mixed; boundary="===============6802738694713022579==" MIME-Version: 1.0 Subject: PGConf NYC 2025 (9/29-10/1) - Schedule Announced! To: PostgreSQL Announce From: United States PostgreSQL Association via PostgreSQL Announce Reply-To: contact@pgconf.nyc Date: Wed, 27 Aug 2025 10:32:37 +0000 Message-ID: <175629075744.807.8656530354164642300@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: conferences X-pglister-tagsig: 7975713b0ecb558ec25af184545160278e0f5ba7b4504221388a9f54063610fe List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============6802738694713022579== Content-Type: multipart/alternative; boundary="===============5414398973669281599==" MIME-Version: 1.0 --===============5414398973669281599== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [PGConf NYC 2025](https://2025.pgconf.nyc/) (September 29 - October 1, 2025= , New York City) is packed with user stories and best practices for how to use [PostgreSQL](https://www.pos= tgresql.org). [Join us in New York City](https://2025.pgconf.nyc/) and conn= ect with other developers, DBAs, administrators, decisions makers, and cont= ributors to the open source PostgreSQL community! We're expecting to sell o= ut - we're not just saying that - so please [register today](https://2025.p= gconf.nyc/tickets/) to secure your spot! The [schedule](https://postgresql.us/events/pgconfus2025/schedule/) is now = available! You can see the schedule here: [https://postgresql.us/events/pgconfus2025/schedule/](https://postgresql.us= /events/pgconfus2025/schedule/) PGConf NYC 2025 also has lots of content relevant to [how you're running Po= stgreSQL](https://postgresql.us/events/pgconfnyc2025/schedule/), including = case studies on managing large fleets and workloads on PostgreSQL, how to i= mprove your query performance, hot topics like the intersection of AI and d= atabases and PostgreSQL support for analytics, advanced deployment models, = different ways to minimize your downtime, and learning about upcoming Postg= reSQL features! [PGConf NYC 2025](https://2025.pgconf.nyc/) is not possible without the [ge= nerous support of our sponsors](https://2025.pgconf.nyc/sponsors/). PGConf = NYC takes place in one of the largest markets of PostgreSQL users. Your spo= nsorship lets you connect with decision makers, developers, DBAs, and Postg= reSQL contributors, helps keep ticket prices low, and helps grow the Postgr= eSQL community. We have sold out our Platinum and Gold sponsorships, but we= still have other sponsorships available. For more information on [sponsors= hip](https://2025.pgconf.nyc/sponsors/), please visit the below link: [https://2025.pgconf.nyc/sponsors/](https://2025.pgconf.nyc/sponsors/) Can't wait to participate in PGConf NYC 2025? [Registration](https://2025.p= gconf.nyc/tickets/) is available: [https://2025.pgconf.nyc/tickets/](https://2025.pgconf.nyc/tickets/) We look forward to seeing you in New York! --===============5414398973669281599== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable PGConf NYC 2025 (9/29-10/1) - Schedule Announced!
 

PGConf NYC 2025 (9/29-10/1) - Schedule Announced!

PGConf NYC 2025 (Septem= ber 29 - October 1, 2025, New York City) is packed with user stories and best practices for how to use PostgreSQL<= /a>. Join us in New York City and connect with other dev= elopers, DBAs, administrators, decisions makers, and contributors to the op= en source PostgreSQL community! We're expecting to sell out - we're not jus= t saying that - so please register today to secu= re your spot!

The schedule is now available! You can see the schedule here:

h= ttps://postgresql.us/events/pgconfus2025/schedule/

PGConf NYC 2025 also has lots of content re= levant to how you're running Pos= tgreSQL, including case studies on managing large fleets and workloads = on PostgreSQL, how to improve your query performance, hot topics like the i= ntersection of AI and databases and PostgreSQL support for analytics, advan= ced deployment models, different ways to minimize your downtime, and learni= ng about upcoming PostgreSQL features!

PGConf NYC 2025 is not = possible without the generous support of our sponso= rs. PGConf NYC takes place in one of the largest markets of PostgreSQL = users. Your sponsorship lets you connect with decision makers, developers, = DBAs, and PostgreSQL contributors, helps keep ticket prices low, and helps = grow the PostgreSQL community. We have sold out our Platinum and Gold spons= orships, but we still have other sponsorships available. For more informati= on on sponsorship, please visit the below link:=

https://2025.pgconf= .nyc/sponsors/

Can't wait to participate in PGConf NYC 202= 5? Registration is available:

https://2025.pgconf.= nyc/tickets/

We look forward to seeing you in New York!<= /p>

This email was sent to you from United States PostgreSQL Association. It wa= s delivered on their behalf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to United States PostgreSQL Association.

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/.
 
--===============5414398973669281599==-- --===============6802738694713022579==--