Daniel Westermann

Disabling “alter system” in PostgreSQL?

Last year there started an interesting discussion on the PostgreSQL development mailing list: Would it make sense to implement something in PostgreSQL which can be used to disable the “alter system” command even for superusers?(…)

PostgreSQL 17: Track skipped rows from COPY in pg_stat_progress_copy

In one of the last posts we’ve looked at how you tell copy to ignore any rows which do not fit into the target table starting with PostgreSQL 17. While this is great, this also hides(…)

PostgreSQL 17: Incremental backups, pg_walsummary

In the last posts about the new incremental backup feature we’ve looked at the following topics: How does it work in general? PostgreSQL 17: Support for incremental backups Backup chains, what is it?(…)

PostgreSQL 17: copy and SAVE_ERROR_TO

Another great feature just got committed for PostgreSQL 17 and hopefully will not be reverted until the final release later this year. You probably already know copy. Whenever you want to load something into or unload something out of(…)

PostgreSQL 17: Incremental backups, system information functions

In the first post about incremental backups we’ve looked at how you can do incremental backups in general starting with PostgreSQL 17, probably, if it does not get reverted for some reason until PostgreSQL 17 is(…)

PostgreSQL 17: Incremental backups and backup chains

In the last post about the introduction of incremental backups for PostgreSQL 17 we’ve looked at the basic concepts of that feature and how you can use it. In the meantime Robert(…)

PostgreSQL 17: Support for incremental backups

When it comes to backing up and and restoring a PostgreSQL cluster, most of our customers rely either on pgBackRest or Barman. The reason for this is pretty clear: Both of those(…)

2023.pgconf.eu – recap

This year’s edition of PostgreSQL Conference Europe finished last Friday, the 15th of December. It was the largest ever PostgreSQL Conference Europe with more than 700 attendees. For me the week already started on Monday, because(…)

PostgreSQL 17: Reset shared statistics at once with pg_stat_reset_shared()

PostgreSQL comes with several catalog views which expose cluster wide statistics. One of them is the new pg_stats_checkpointer view we’ve talked about previously. To reset some of those statistics there is pg_stat_reset_shared().

PostgreSQL 17: New catalog view pg_stat_checkpointer

Up to PostgreSQL 16 checkpointer related statistics are available in pg_stat_bgwriter. As the work of bgwriter and checkpointer has been split into two separate processes back in 2011 for PostgreSQL 9.2 (see 806a2aee3791), it makes sense(…)