SIze 0 in pg_stat_file, pg_stat_progress_copy

Started by Marc Millasalmost 3 years ago2 messagesgeneral
Jump to latest
#1Marc Millas
marc.millas@mokadb.com

Hi,

on a debian machine, with a postgres 14,2 server

logs in a dedicated directory (not log)
when logged as superuser, I get:
--pg_stat_file for the current logfile says size 0,
--pg_ls_logdir answers 0 files,
--pg_ls_dir, for the log directory provides postgres.csv, postgres.json,...
list of files
--and when running a copy from the current logfile with a where clause to
choose only the current day logs, the bytes total column is 0

what can provides such a behaviour ?

thanks,

Marc MILLAS
Senior Architect
+33607850334
www.mokadb.com

#2Marc Millas
marc.millas@mokadb.com
In reply to: Marc Millas (#1)
Re: SIze 0 in pg_stat_file, pg_stat_progress_copy

Sorry...
someone did setup the log as a named pipe...

Marc MILLAS
Senior Architect
+33607850334
www.mokadb.com

On Fri, Apr 14, 2023 at 4:26 PM Marc Millas <marc.millas@mokadb.com> wrote:

Show quoted text

Hi,

on a debian machine, with a postgres 14,2 server

logs in a dedicated directory (not log)
when logged as superuser, I get:
--pg_stat_file for the current logfile says size 0,
--pg_ls_logdir answers 0 files,
--pg_ls_dir, for the log directory provides postgres.csv,
postgres.json,... list of files
--and when running a copy from the current logfile with a where clause to
choose only the current day logs, the bytes total column is 0

what can provides such a behaviour ?

thanks,

Marc MILLAS
Senior Architect
+33607850334
www.mokadb.com