Re: Call for Posters: PGConf.dev 2026 - Mailing list pgsql-hackers

From Andrey Borodin
Subject Re: Call for Posters: PGConf.dev 2026
Date
Msg-id 8EC482B7-A1F9-49F5-A47E-A360640F2B3D@yandex-team.ru
Whole thread
In response to Call for Posters: PGConf.dev 2026  (Andrey Borodin <x4mmm@yandex-team.ru>)
List pgsql-hackers

> On 5 Feb 2026, at 22:45, Andrey Borodin <x4mmm@yandex-team.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


pgsql-hackers by date:

Previous
From: Richard Guo
Date:
Subject: Wrong results from inner-unique joins caused by collation mismatch
Next
From: David Rowley
Date:
Subject: Selective tuple deformation