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 1uUgCC-006vrX-RE for pgsql-admin@arkaria.postgresql.org; Thu, 26 Jun 2025 06:34:52 +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 1uUgCA-008asj-D0 for pgsql-admin@arkaria.postgresql.org; Thu, 26 Jun 2025 06:34:51 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uUgC9-008asb-VF for pgsql-admin@lists.postgresql.org; Thu, 26 Jun 2025 06:34:50 +0000 Received: from mail-pg1-x532.google.com ([2607:f8b0:4864:20::532]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uUgC8-004AcU-17 for pgsql-admin@lists.postgresql.org; Thu, 26 Jun 2025 06:34:50 +0000 Received: by mail-pg1-x532.google.com with SMTP id 41be03b00d2f7-b2c4e46a89fso531805a12.2 for ; Wed, 25 Jun 2025 23:34:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1750919686; x=1751524486; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=uKqv/eIJ4HzAyaKn8GhAJxRZ0OvdVN7Kt5GIHBJxFIA=; b=B4qiYdyRHPIjh81qH+owZ9Bacmfg245xBUXtF612qiR63gRI5VUo232uu1SsQp9BF6 4jg/oaeHaHKxgFdYr/fuHHeOjWh9tCF6FGk4HBU377hc/kyfORmQqNrzHIaWWPJ3pj77 5tAH2ZJspn1e1u2iwUeOI5c1WHl1KGQnUkemh/KgNZHEkqDEtvweOvSbmfnYZ0uLRdKe vx/4HycvzJI+nDEbWUCJSDBGQ3ud3bUsVH1Pr0lth9hTdeNj6UYuXFxrN5tAreMEBoJB HeBujCvUkX4/pXKAl1h9WYG2g6kQZAgPBbdCuwSK6zEl9o5otq6tlZfByS3B8joVPCux 5TIQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1750919686; x=1751524486; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=uKqv/eIJ4HzAyaKn8GhAJxRZ0OvdVN7Kt5GIHBJxFIA=; b=BFjHC0RJQiPT3s7VEDhfIEmR39oSAHRTBWajKmkgk1sGo/Fo8tsMNWXaW/GanVFKf+ 6sZelKcayXecRGXn74mCIhpnFSwTxjm+5u5ikx4rlO/pDoH5kIOLaircHURSN3Cj4neG h5LPa/Jg6GYUXhxjQ7srd6+gVNxpSOS9awc0RH03pDhEorELSkE5XACROJN/cGKskz7I EZwbPgxxR58Z5J3Jm9Sr0uzcvFf1yIpPCJ11I86viV8KXfkc/MlyPPJZHhi+GBhudTfp HvQqBX5+KRstcEdlj+b9kUieTt2/5JTTTXSd1KyPVv9rqURveIYxgbm1ELVE8J4EoKcq KMNg== X-Gm-Message-State: AOJu0YxXj5SG1wTxWHFy/WPxn2LYKdRbzdDWZhnJmReGvzUdfFkVn9Pc C/hcUhNE6J5pyDxThr9NHv+o1msoEj0MlcvRcP7DNlKd8ok3ijtnuAJM8mLbwmTzpRanJH595HE BFAd20O4yHuC7KwvuuWcdAkq7njah43g= X-Gm-Gg: ASbGncttGaqDHc17/q8+iS5reqf5hgLe1VJX3eRLrafC0S/sQDzElBkmT+nGuXzTJSq gO+zhR8As6qe13Jil389gFxLoJ2csLTysggNcH4FZUD6mztICgJ736mzkWh1Ep0iRTa7agE2v8I bCzHpuBswjSGYsihFf61BttRe+Prv/n26VJEgSMUKuvh5caWOsdCYnzYYgnfJdQuRSTbGvie0M2 FQ= X-Google-Smtp-Source: AGHT+IHecV7ejTOZ2WIrGtk5fqhJjjNzCuEHUxGMLP/2uQ0BN9oFGntkO2BAOvdSmHIOn+lsw5foUmK+na87s/6izJc= X-Received: by 2002:a17:90b:38ce:b0:311:fde5:c4be with SMTP id 98e67ed59e1d1-315f26c1c46mr7313255a91.35.1750919685640; Wed, 25 Jun 2025 23:34:45 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Motog Plus Date: Thu, 26 Jun 2025 12:04:34 +0530 X-Gm-Features: Ac12FXw-yuYTjQZj5F6_sVqVnxlxi9kz3kmQPo8E6afscz_sTmAQcRf5RTG2EpA Message-ID: Subject: Re: Guidance Needed: Scaling PostgreSQL for 12 TB Data Growth - New Feature Implementation To: "David G. Johnston" Cc: Pgsql-admin Content-Type: multipart/alternative; boundary="000000000000e497a8063873c165" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000e497a8063873c165 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Dear David, My apologies for the quick follow-up. You're absolutely right, and I completely understand that community members contribute their valuable time as volunteers. There was no intention to rush or disrespect anyone's efforts. I'm simply very keen to address this significant scaling challenge for our application and was perhaps a bit too eager for guidance. I will certainly be more patient moving forward. Thank you for your feedback Regards, Ramzy On Thu, Jun 26, 2025, 11:10 David G. Johnston wrote: > On Wednesday, June 25, 2025, Motog Plus wrote: >> >> >> We are still actively seeking your valuable insights and guidance on >> managing our anticipated data growth. >> > > If you can=E2=80=99t even wait a full day without pinging your request fo= r input > you might consider paying professionals instead of using volunteers. > > David J. > > --000000000000e497a8063873c165 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear David,

=
My apologies for the quick follow-up. You're ab= solutely right, and I completely understand that community members contribu= te their valuable time as volunteers. There was no intention to rush or dis= respect anyone's efforts.

I'm simply very keen to address this significant scaling challeng= e for our application and was perhaps a bit too eager for guidance. I will = certainly be more patient moving forward.

=
Thank you for your feedback

Regards,
Ramzy

=
On Thu, Jun 26, 2025, 11:10 David G. Johnston <david.g.johnston@gmail.com> wrote:<= br>
On Wednesday, June 25, 2025, Motog = Plus <mplus7535@gmail.com> wrote:
=

We are stil= l actively seeking your valuable insights and guidance on managing our anti= cipated data growth.

If you can= =E2=80=99t even wait a full day without pinging your request for input you = might consider paying professionals instead of using volunteers.
=
David J.

--000000000000e497a8063873c165--