Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Postgresql.csv log consumes all disk space

See original GitHub issue

Bug report

Describe the bug

When running supabase, the docker overlay 2 runs full. I could track it down to the postgresql.csv logs under var/lib/docker/overlay2/**/diff/var/log/postgresql. It seems that logs don’t have an upper limit.

Expected behavior

I would expect, that the logs won’t grow indefinitely. At least, there most be some settings to specify the upper size.

Screenshots

My LXC container had 15GB diskspace and the csv file contained 6.4 GB.

System information

OS: Ubuntu 20.10 Server in an LXC Container

Additional context

Issue Analytics

State:
Created 2 years ago
Comments:14 (2 by maintainers)

Top GitHub Comments

1reaction

kiwicopplecommented, Jan 17, 2022

Hey @Manuelbaun - this one is probably not a bug. It’s up to you to manage the configuration of your Postgres instance to suit your particular use-case.

You could check out the log_rotation_size config option (https://postgresqlco.nf/doc/en/param/log_rotation_size/) and possibly dig into a logrotate solution like https://vector.dev (which is very good!)

0reactions

ymilhahncommented, Oct 29, 2022

Seems like https://github.com/supabase/supabase/commit/4a70284e47f9ef00d1ff7f65096e4319e25333fd fixes this issue in a better way? It’s excluding just the realtime polling queries, which seem to be the cause of fast growing log files in the first place?

Can be closed?