Is `pgrcolumnar` the default storage layout for tables? It would be cool if the same storage engine outperforms vanilla Postgres under both OLTP and OLAP workloads.

AlloyDB from Google Cloud uses columnar storage like a secondary index, while the relations are still stored in TOAST.

pgrcolumnar is not the default storage method. Right now, it's exposed as a table access method. There's lots of design space for how to do this so I want to avoid pre-committing to anything

I'm surprised no one mentioned https://github.com/pumpkin-mc/pumpkin in this thread. It's the fastest Minecraft server implementation and it's written in Rust.

Typst has probably saved us thousands of dollars generating PDF documents programmatically.

You might already do this, but great opportunity to support them with a donation.

We are indeed a monthly GitHub sponsor.

Is this because it has replaced paid SaaS for you?

Yes. Although many document generation SaaS platforms are not transparent about their pricing, they often charge a few cents per document. This is somewhat unacceptable given that the marginal cost is almost zero.

Cool website! Did you use any web framework or just plain HTML/CSS?

Just plain HTML/CSS.

I did this morning in a rush. Didn't expect anyone to compliment it. Thank you!

If generating PDF dynamically is what you really care about, consider Typst. https://typst.app/ We use it in production to generate reports, and it is amazing.

See https://lwn.net/Articles/1037577/ for a recent summary of what you can do with Typst.

What's the problem with Inter?

We [1] have been using Typst to generate PDF documents in production for a few months, such as invoices and labels. It's generating thousands of documents daily, and I'm glad that some of them are printed and used by people in the warehouse who are doing real work.

I really like the simple syntax that Typst provides. It would be much harder for the PMs to edit the templates if we went with other solutions, such as wkhtmltopdf.

We also looked into other document generation services that provide a WYSIWYG interface, and they are all quite expensive and often lack advanced scripting capabilities.

[1] https://garnercorp.com/

How have you found the generation performance? It seems like this should really be a perfect fit for this sort of use-case, and I'd hope the memory footprint and speed are all much more competitive than HTML-based approaches.

The team I'm currently working with are using Gotenberg for things which we can afford to take a little while, and C#/Skia for things which need to be reasonably quick.

Most of the documents are generated in an instant, plus we deployed this on Kubernetes with HPA, so high load isn't an issue.

The main issue I found with an HTML-based approach is that browsers are not designed for papers. It would be very challenging, but still possible [1], to customize the page layout, headers, and footers. Nonetheless, we have even more advanced use cases that only Typst/LaTex could cater to, such as displaying the table header of a table that spans multiple pages on every page.

[1] https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_media_q...

I only experienced a couple milliseconds for small documents of 15 pages or so. It’s reasonably fast to show the user the result „immediately“ on changes. Haven’t checked memory usage.

Thanks for your comment! I have a few PDFs that I need to generate for groups of users every so often and since wkhtmltopdf is considered EOL, I've been forced to use chrome (which sucks to manage). I just rewrote that code to use Typst (via the typst gem) and it's so so so much better.

An SSH tunnel is more than enough for that purpose.

Do you consider new grads for this role?

I'll consider anyone if it's the right person.