Re: Call for Posters: PGConf.dev 2026

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Call for Posters: PGConf.dev 2026
Date: 2026-04-24 11:58:15
Message-ID: 8EC482B7-A1F9-49F5-A47E-A360640F2B3D@yandex-team.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 5 Feb 2026, at 22:45, Andrey Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
>
> As we prepare for the PostgreSQL Development Conference 2026
> (PGConf.dev 2026), scheduled for May 19–22 in Vancouver, Canada, we
> are excited to host a poster session showcasing the contributions and
> projects within our community.

Hi all,

Quick update: about 12 people have signed up so far, which means there
are roughly 8 spots remaining. We would love to fill them with
interesting technical and community posters.

I have just sent a reminder email to everyone I have on my list. If you
expressed interest but did not receive it, please check your junk folder
and ping me directly - I likely just missed you.

If your patch needs attention - reviewers, co-authors, committer
feedback - a poster is a concrete way to get it. People stop, read,
and talk. We plan to do Poster Session Showcase during thursday lunch,
see full schedule here [0].

Here is what makes a good poster for this session:

Show the technical substance: architecture diagrams, benchmark
results, open design questions.

Make clear what kind of help or feedback you are looking for:
"needs review", "looking for co-author", "RFC", etc.

Structure it yourself - even if you use AI tools, please do not
generate the whole thing in one prompt from a hackers thread dump.
AI tends to produce something that looks like a movie poster.
Your own structure will express the problem better and give
people more to react to.

Include contact info and a QR code to your patch or project page.

Use the PGConf.dev 2026 logo, portrait orientation, A1 size.

I will start printing in early May.

Come to Vancouver, put your work on the wall, and let us discuss.

Best regards, Andrey Borodin.

[0] https://2026.pgconf.dev/schedule/thursday

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2026-04-24 12:06:57 Selective tuple deformation
Previous Message Richard Guo 2026-04-24 11:42:28 Wrong results from inner-unique joins caused by collation mismatch