[ADMIN] I've got gaps in the log files?

[Andreas]

Hi,
it appeares I've got gaps in the log files.

It's a PG 9.1 from the OpenSuse 12.1 distribution.

I know the server is running so it should dump it's feelings all the
time in those files in PGDATA/pg_log.
But I find huge gaps where nothing is written.

E.g. yesterday the last entry is at 09.54pm. Thats the change timestamp
of the file, too.

Today there is a new file whichs first line is 11.37am while I
definitely know there were users connected way earlier and there should
be comlaints about lost connections all the time as it is "normal" with
MS-Access as client via odbc.

Actually I was working at it yesterday after 10pm so there should be
log-lines for my DDL queries from that timespan.

OK, my issue might sound weired but I'd rather like to know where this
log stuff could have gotten lost.

[Tom Lane]

Post by Andreas
it appeares I've got gaps in the log files.
It's a PG 9.1 from the OpenSuse 12.1 distribution.
I know the server is running so it should dump it's feelings all the
time in those files in PGDATA/pg_log.
But I find huge gaps where nothing is written.

The only suggestion that comes to mind offhand is to check the logfile
rotation parameters in postgresql.conf. Maybe the missing log entries
went to a file that got truncated and rewritten afterwards because of
poorly selected rotation parameters.

regards, tom lane

[Andreas]

Post by Tom Lane

Post by Andreas
it appeares I've got gaps in the log files.
It's a PG 9.1 from the OpenSuse 12.1 distribution.
I know the server is running so it should dump it's feelings all the
time in those files in PGDATA/pg_log.
But I find huge gaps where nothing is written.

The only suggestion that comes to mind offhand is to check the logfile
rotation parameters in postgresql.conf. Maybe the missing log entries
went to a file that got truncated and rewritten afterwards because of
poorly selected rotation parameters.

I left them on defaults.
Actually they are even commented out.

#log_truncate_on_rotation = off
#log_rotation_age = 1d
#log_rotation_size = 10MB

It's not as if I expect particularily huge log files anyway.
On most days its just the one that got created when the rotation starts
a new one like
postgresql-2012-03-07_000000.log


regards Andreas

[Greg Sabino Mullane]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Post by Andreas
I left them on defaults.
Actually they are even commented out.

Never assume that the commented out version == default == actual value.

Always explicitly set parameters you care about.

- --
Greg Sabino Mullane ***@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201203062241
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAk9W2QMACgkQvJuQZxSWSsg8/wCgsw4+Z0WQw4WudPOOdveh9twR
WxgAnjMfVtXsGSF7TxbOI7vTDR6vuH7m
=eMNV
-----END PGP SIGNATURE-----