I’m back from pgDay Paris. I really enjoyed this edition. I’d already come to the 2019 one, and I must say I wasn’t deceived. As a reminder, pgDay Paris is an international conference. Presentations are in English, attracting more English speakers and audiences.
I often see this conference as a little PGConf Europe: the content is dense with an international dimension.
You meet familiar faces: attendees, speakers, volunteers, contributors: all the people who keep the Postgres community going.
It’s also an opportunity to put faces on names you’ve come across while reading articles or Postgres mailing lists.
Here’s a quick recap of the conferences I attended:
With Carole and Stéphanie, we thought it would be good to have this conference as an introduction.
I found it very complete. It talks about Postgres, but also and above all about its community. That’s what makes Postgres so powerful.
Slides are availables.
Sustainable Database Performance profiling in PostgreSQL
Postgres provides a variety of statistical views to give you information on its activity.
These can be native (pg_stat_statements …) or via extensions pg_stat_kcache, pg_wait_sampling.
However, and this is what this conference emphasizes, they provide a view at a given moment in time.
To use them, they need to be historized. The speaker presents a tool based on what is done on Oracle: pg_profile.
On the other hand, he presents it as the only tool that can be used to process such information. A participant in the audience pointed out that there was another project: PoWA.
The two tools don’t provide the same functions, pg_profile generates an HTML report. It’s fairly easy to install, and requires no external libraries, as it’s written in pl/pgsql.
PoWA provides graphs, index suggestion… but is heavier to install.
Slides are available.
PostgreSQL without permanent local data storage
Now we’re getting into a very tec
[...]