On Thu, May 4, 2023 at 4:23 PM Thomas Munro wrote:
> On Fri, May 5, 2023 at 8:37 AM ProfiVPS Support
> wrote:
> > I feel like ANYTHING would be better than this. Even risking loosing
> _some_ of the latest data in case of a server crash (if it crashes we lose
> data anyways until restart, ofc w
On Fri, May 5, 2023 at 8:37 AM ProfiVPS Support wrote:
> I feel like ANYTHING would be better than this. Even risking loosing _some_
> of the latest data in case of a server crash (if it crashes we lose data
> anyways until restart, ofc we could have HA I know and we will when there'll
> be a
Hi,
thank you for your response :)
Yes, that's exactly what's happening and I understand the issue with
fsync in these cases. But I see no workaround about this as the data is
ingested one-by-one (sent by collectd) and a db function handles it (it
has to do lookup and set state in a differe
Hi,
On 2023-05-04 19:31:45 +0200, ProfiVPS Support wrote:
> We are collecting around 400k values each 5 minutes into a hypertable. (We
> use timescaledb extension, I also shared this on timescale forum but then I
> realised the issue is postgresql related.)
I don't know how timescale does its st
Oh, sorry, we are using PostgreSQL 13.10 (Debian 13.10-1.pgdg100+1) on
the server with with TimescaleDB 2.5.1 on Debian 10.
2023-05-04 19:31 időpontban ProfiVPS Support ezt írta:
Hi there,
I've been struggling with very high write load on a server.
We are collecting around 400k values each
