## Tom Lane (t...@sss.pgh.pa.us):
> Jason McLaurin writes:
> > I'm troubleshooting an issue where about once a week, a database appears to
> > lock up and then the PostgreSQL process crashes and recovers. When this
> > happens, a few queries will be logged, but there is no pattern to which
> > qu
On 4/2/23 21:40, Tom Lane wrote:
Jason McLaurin writes:
Is there anywhere you'd suggest we start looking for hints? I'd be
interested in increasing relevant logging verbosity so that we can see when
key background processes are running, both in Postgres core and Timescale.
It might be helpful
Jason McLaurin writes:
> Is there anywhere you'd suggest we start looking for hints? I'd be
> interested in increasing relevant logging verbosity so that we can see when
> key background processes are running, both in Postgres core and Timescale.
It might be helpful to try to identify which wait
Hi Tom,
>
>
> Hmm, is it always the checkpointer that gets the OOM kill? That seems
> quite odd.
>
> What PG version is this exactly? Do you have any extensions installed?
>
> I recall having seen somebody before reporting odd slowness of trivial
> commands like BEGIN. I failed to find the thre
Jason McLaurin writes:
> I'm troubleshooting an issue where about once a week, a database appears to
> lock up and then the PostgreSQL process crashes and recovers. When this
> happens, a few queries will be logged, but there is no pattern to which
> queries are executing when the crash happens, a
Hello,
I'm troubleshooting an issue where about once a week, a database appears to
lock up and then the PostgreSQL process crashes and recovers. When this
happens, a few queries will be logged, but there is no pattern to which
queries are executing when the crash happens, and the queries logged do
