Getting a postgres error I don't recognise
joelanman
HOBBYOP

2 years ago

Getting these from time to time, is it bad? Any tips to investigate or fix?

2024-06-12 15:28:31.219 UTC [28] LOG:  checkpoint starting: time

2024-06-12 15:28:31.331 UTC [28] LOG:  checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.103 s, sync=0.003 s, total=0.113 s; sync files=2, longest=0.003 s, average=0.002 s; distance=7 kB, estimate=22 kB; lsn=0/47C6DF8, redo lsn=0/47C6DC0

15 Replies

joelanman
HOBBYOP

2 years ago

61398dc5-6b4a-40c8-a31f-d56ffd752011

brody
EMPLOYEE

2 years ago

i dont see an error there?

joelanman
HOBBYOP

2 years ago

no me neither, but its marked as an error in the logs

joelanman
HOBBYOP

2 years ago

1250475043327185000

joelanman
HOBBYOP

2 years ago

using this
https://hub.docker.com/r/postgis/postgis

joelanman
HOBBYOP

2 years ago

possibly theyre going in Error by mistake somehow?

passos
MODERATOR

2 years ago

there's no error, thats just Railway showing the logs error or postgres sending logs in wrong level

brody
EMPLOYEE

2 years ago

yep! please take into account the log itself, not the colour

joelanman
HOBBYOP

2 years ago

right, but I'd rather not have errors in the error log that arent errors

brody
EMPLOYEE

2 years ago

postgres logs to stderr for some reason, so they are coloured red

joelanman
HOBBYOP

2 years ago

huh thats weird

brody
EMPLOYEE

2 years ago

thats beyond railway's control

joelanman
HOBBYOP

2 years ago

ok cool ta

joelanman
HOBBYOP

2 years ago

do I just add 'Solved' tag or should I close threads too?

brody
EMPLOYEE

2 years ago

please dont close posts

Loading...