Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tciLn-00281U-8R for pgsql-general@arkaria.postgresql.org; Tue, 28 Jan 2025 09:57:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tciLm-0002ar-0F for pgsql-general@arkaria.postgresql.org; Tue, 28 Jan 2025 09:57:42 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tciLl-0002ai-M0 for pgsql-general@lists.postgresql.org; Tue, 28 Jan 2025 09:57:41 +0000 Received: from mail-ej1-x633.google.com ([2a00:1450:4864:20::633]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tciLj-001uwh-0t for pgsql-general@postgresql.org; Tue, 28 Jan 2025 09:57:40 +0000 Received: by mail-ej1-x633.google.com with SMTP id a640c23a62f3a-aaf900cc7fbso877979866b.3 for ; Tue, 28 Jan 2025 01:57:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1738058258; x=1738663058; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=ldZeBQaTdcN01rZMb7SZYqggNDVjDMs6yMgE6631toA=; b=hokbfG3yVwNv1RoOT/hgIhZcFvT7R0N4eX+QCFjSEdsTzyTv/e7rm2lpByIB5/pky+ fuNRMMC4RK29xrIzv70jeIkb22RH6Wntpp+5ai74B1ZcodZx7fXuN8uUTVrKgamtr0Vn sc3Rik/weTX/XLghWtmrV22ELOfZ8wjCLjQa/cxXaLtDXg4ig9sTCwhIpxkMlDFtQnBs neEqpbMjhCvCMv8yvlurFFFjh8lXsN6dymBpwRhl3ChRKzlcs68c1xCKpRdyVjEFZ3JZ aZ+G7N1/UCkL+ma8HLrjFYYIAUK76R59NiDLYay+Aa+SDJnjd7z+So+uiMkEQYRZlGvp MgJQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738058258; x=1738663058; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=ldZeBQaTdcN01rZMb7SZYqggNDVjDMs6yMgE6631toA=; b=hVjJ6OGsErxtpNNBX6G8+A6Rpr2UfPKxa0velpLD9nhLsa9BF4GklIiFYrC0Q0uqp/ 3LrrHl7ZvOXJsAaU0vRoLthQ0DfL6uquZJzIMe+myvED5p6XqRvxbO7fPBzXg0ilsqVu Nlze+1hgdOW+12f7oD06+/ZeVNzP67KhddEBTz8cXRVfDyHdKEW71GKdjKerIEoMRzGC uVCUHOOH2dMttWSHpWdIxVOAnglTrXn8z0EXAuerr+1EDd5+JTSyOyfYV5YeG5fROhSO 66Sfqon1ZGaOvPARYr6EHwuMmU64Bv3qrlGeY4B+mWP0ne1KcuXm2xxnaaYYGuyvNzet zhZg== X-Gm-Message-State: AOJu0YxxwkY0cN/cEADo1VcvViOr+YlqA7/bk8QVo5Kv1pJbY6kFZtOm UodS5Ut/e32D0A1ND0XwhkglwAxS/Iyi5sKJ6O6+qQ85HXcbw47ojpZhqsBvCjqkWDMPWXMtQOy U/NHjK9vluG0lfU75M/0jIIgL5IyIp9Jr5Xs= X-Gm-Gg: ASbGncv5UXFu1yhRpj8VgukA2IcdHgGyIKzsa+CrJEgpuLqIg6PXVweGgOl3otkZ0Ir olNF6bMcaxdNNlXT5gXsY7+O4hpBEs0RO6R+i6cZl/YQFn3ii0ze5lnA8vbudYtyvWo9y8Fw= X-Google-Smtp-Source: AGHT+IFRC1+ViuXQhcOP7VLA8shs6BpI3S9DP0CItRvu11F/tENjmxIIUY3xuy09A5p5xCukLLF0HKORdCMiJxXWqBw= X-Received: by 2002:a17:907:d9f:b0:aa6:7ec4:8bac with SMTP id a640c23a62f3a-ab38b1100c3mr4300029266b.17.1738058257842; Tue, 28 Jan 2025 01:57:37 -0800 (PST) MIME-Version: 1.0 From: Paul Brindusa Date: Tue, 28 Jan 2025 09:57:26 +0000 X-Gm-Features: AWEUYZmeLHYzNWy97XDD0qvrvl0nzbCHpJ6YcO-kFvdipgawrVjvXHBKTEvvYZE Message-ID: Subject: Log retention query To: pgsql-general Content-Type: multipart/alternative; boundary="0000000000000ec9b5062cc13993" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000000ec9b5062cc13993 Content-Type: text/plain; charset="UTF-8" Good morning everyone, Before I get on with today's problem, I would like to say how much I appreciate this community and everything that you do for end users. In today's problem I would like to understand if the following lines in our config handle the log rotation for our clusters? log_checkpoints: on logging_collector: on log_truncate_on_rotation: on log_rotation_age: 1d log_rotation_size: 1GB log_error_verbosity: verbose I have been deleting the logs manually for the last month, since I am confused how the log collector rotates them. Am looking to delete logs older than 180 days. What are we doing wrong in the config? -- Kind Regards, Paul Brindusa paulbrindusa88@gmail.com --0000000000000ec9b5062cc13993 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Good morning everyone,

Befor= e I get on with today's problem, I would like to say how much I appreci= ate this community and everything that you do for end users.

=
In today's problem I would like to understand if the followi= ng lines in our config handle the log rotation for our clusters?
=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 log_checkpoints: on
=C2=A0 = =C2=A0 =C2=A0 =C2=A0 logging_collector: on
=C2=A0 =C2=A0 =C2=A0 =C2=A0 l= og_truncate_on_rotation: on
=C2=A0 =C2=A0 =C2=A0 =C2=A0 log_rotation_age= : 1d
=C2=A0 =C2=A0 =C2=A0 =C2=A0 log_rotation_size: 1GB
=C2=A0= =C2=A0 =C2=A0 =C2=A0 log_error_verbosity: verbose

I have been deleting the logs manually for the last month, since I am conf= used how the log collector rotates them.=C2=A0

Am = looking to delete logs older than 180 days. What are we doing=C2=A0wrong in= the config?

-- =
Kind Regards,
--0000000000000ec9b5062cc13993--