You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently, upgrading PostgreSQL 13 clusters to PostgreSQL 18, I noticed that the sequence values of the pgagent extension were not transferred to the new installations. This lead to failures running pgagent jobs in the new installations since logging failed due to duplicate primary keys.
In the attachment you will find my solution to the problem: 1. calling pg_extension_config_dump() in an extension update script, and 2.) making the new extension version the default. Please adapt this according to your preferences.
Recently, upgrading PostgreSQL 13 clusters to PostgreSQL 18, I noticed that the sequence values of the pgagent extension were not transferred to the new installations. This lead to failures running pgagent jobs in the new installations since logging failed due to duplicate primary keys.
In the attachment you will find my solution to the problem: 1. calling
pg_extension_config_dump()in an extension update script, and 2.) making the new extension version the default. Please adapt this according to your preferences.add_seq_data_to_dump.patch