Abhishek Bhola <abhishek.bhola@japannext.co.jp> writes: > This morning I noticed this error in my PG CSV log file. > 2022-05-25 23:59:17.776 JST,,,117110,,628cf2c5.1c976,1,,2022-05-25 23:59:17 > JST,9/611296,0,ERROR,XX001,"uncommitted xmin 16395356 from before xid > cutoff 144683296 needs to be frozen",,,,,"while scanning block 19267 of > relation ""relation_name""
> This was a data corruption error that I resolved by truncating the table > and reloading it. However, I was curious why this message was not sent to > my syslog.
Seems to me this filter explains that well enough:
> ## Added by DataConsulting Team for syslog filter > if $programname == 'postgres' and \ > ($msg contains 'CODE:28000' or \ > $msg contains 'CODE:28P01' or \ > $msg contains 'CODE:3D000' or \ > $msg contains 'CODE:08006' or \ > $msg contains 'CODE:42501' \ > ) then /xxxx/xxxx/xxx/pg_log/postgres_filter.log
You should realize of course that syslog is not a 100% reliable logging mechanism -- at least most implementations are capable of dropping messages under load. But we needn't guess about reasons for missed messages here.
regards, tom lane
This correspondence (including any attachments) is for the intended recipient(s) only. It may contain confidential or privileged information or both. No confidentiality or privilege is waived or lost by any mis-transmission. If you receive this correspondence by mistake, please contact the sender immediately, delete this correspondence (and all attachments) and destroy any hard copies. You must not use, disclose, copy, distribute or rely on any part of this correspondence (including any attachments) if you are not the intended recipient(s).本メッセージに記載および添付されている情報（以下、総称して「本情報」といいます。）は、本来の受信者による使用のみを意図しています。誤送信等により本情報を取得された場合でも、本情報に係る秘密、または法律上の秘匿特権が失われるものではありません。本電子メールを受取られた方が、本来の受信者ではない場合には、本情報及びそのコピーすべてを削除・破棄し、本電子メールが誤って届いた旨を発信者宛てにご通知下さいますようお願いします。本情報の閲覧、発信または本情報に基づくいかなる行為も明確に禁止されていることをご了承ください。