MIME-Version: 1.0
From: Robert Haas <robertmhaas@gmail.com>
Date: Thu, 9 Apr 2026 15:29:44 -0400
Message-ID: 
 <CA+TgmoZn6PbYEHO5aBOOFh2mE6eeLgi9mDnhQv2riKxRikUM4Q@mail.gmail.com>
Subject: PgConf.Dev 2026 - last call for community discussion sessions
To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: 
 <https://www.postgresql.org/message-id/CA%2BTgmoZn6PbYEHO5aBOOFh2mE6eeLgi9mDnhQv2riKxRikUM4Q%40mail.gmail.com>
Precedence: bulk

Hi,

While 2026.pgconf.dev has already selected its full lineup of talks,
the call for papers for community discussion sessions remains open
until April 14th,[1] which is now just a few days away. The reason for
this is that there was a concern that community discussions might be
needed to cover topics that came up at the last minute, or that looked
different after feature freeze than they did before. I assume a lot of
people are still pretty wiped out from all the work they did leading
up to the feature freeze, but we really can't leave the call for
community discussion sessions any longer than the current deadline,
because we need to have time to decide what to accept, schedule the
things that do get accepted into rooms, and publish the final
schedule. Therefore, if there is something you want to discuss on May
19th with your fellow pgconf.dev attendees, please submit a CDS
proposal today.[2]

Think of this as a proposal for a hallway track discussion except you
don't have to have it in the hallway: we provide you with a time slot
and a room!

One final note: You can mention in your submission who your key
attendees are and we will attempt to schedule at a time that they can
make. However, you MUST check with your key attendees before
submitting. Don't send us a proposal that says that Tom Lane will be
joining your discussion unless you've corresponded with Tom Lane and
he has said that he will in fact be doing that. Contrariwise, if
somebody tells you that they want to list you as a key attendee,
please look at the schedule[3] before accepting. If you're already
committed to going to a bunch of things or if the other stuff that's
already happening looks more interesting than the proposed session,
just say no. The person can still submit the session, but you'll spare
me and the rest of the Tuesday planning committee[4] the joy of trying
to schedule around a constraint that doesn't really exist. I can
absolutely promise you that scheduling around the real constraints is
hard enough already.

Thanks, and looking forward to seeing many of you at the event!

-- 
Robert Haas
PGConf.Dev 2026 Organizing Committee

[1] https://2026.pgconf.dev/cfp.html
[2] https://www.pgevents.ca/events/pgconfdev2026/callforpapers/ => New
Submission
[3] https://2026.pgconf.dev/schedule/tuesday
[4] https://2026.pgconf.dev/about => scroll down to "Tuesday Planning Committee"