Hi all,
till today I was running in production one only
db so the autovacuum log was fine. Since today
I have two db but looking at the following line:
Performing: VACUUM ANALYZE public.current_connection
I don't have idea about the database involved, I suggest:
Performing: VACUUM ANALYZE
Gaetano Mendola wrote:
I don't have idea about the database involved, I suggest:
Performing: VACUUM ANALYZE dbame.public.current_connection
or
Performing: VACUUM ANALYZE public.current_connection@dbname
I know that I will know the database on the very next line, but sometimes
is too late :-(
I
Matthew T. O'Connor wrote:
Gaetano Mendola wrote:
I don't have idea about the database involved, I suggest:
Performing: VACUUM ANALYZE dbame.public.current_connection
or
Performing: VACUUM ANALYZE public.current_connection@dbname
I know that I will know the database on the very next line, but
Gaetano Mendola wrote:
Well but a default line will be in the postgresql.conf, you'll insert the
dbname in the default one ?
That is an option. I'm not sure I should clutter the log file with the
database name for every log entry, but then again, autovacuum does work
on the system tables and
