For the ones triggered after hours the only other events close by would
be pg_dump kicking off a backup (full database dump). I do see now that
quite a few of the warnings are triggered right after the pg_dump
process ends.
The ones during the day (specific schemas or individual table) would be
triggering before pg_dump ends although they are multi-step backups. If
only one of the requested backups were triggering the warning it might
explain why it happens before the end.
Any suggestions on which "when to log" settings and levels should be
changed in postgresql.conf to get better info?
Currently they are client_min_messages = warning
log_min_messages = warning
log_min_error_statement = warning
Mike
On Thu, 2006-02-23 at 17:27 -0500, Tom Lane wrote
> "Mike G." <mike@thegodshalls.com> writes:
> > I have the postgresql.conf escape_string_warning active on my Win32 machine. I have a couple databases on it which
arestatic. When pg_autovacuum checks these static databases it is triggering the warning: "non standard use of \\ in a
stringliteral at character 128 or character 355" depending upon which database it is checking.
>
> This is a tad hard to believe, as the 8.1 version of pg_autovacuum
> doesn't generate any commands that need to be parsed. Nor can I
> reproduce this while testing. Can you provide more context?
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend