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 1rPmqH-00E8fc-BT for pgsql-general@arkaria.postgresql.org; Tue, 16 Jan 2024 17:03:14 +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 1rPmqG-005N2D-2d for pgsql-general@arkaria.postgresql.org; Tue, 16 Jan 2024 17:03:12 +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 1rPmqF-005N1s-Ok for pgsql-general@lists.postgresql.org; Tue, 16 Jan 2024 17:03:11 +0000 Received: from mail-pl1-x631.google.com ([2607:f8b0:4864:20::631]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rPmqD-001qRE-7u for pgsql-general@lists.postgresql.org; Tue, 16 Jan 2024 17:03:10 +0000 Received: by mail-pl1-x631.google.com with SMTP id d9443c01a7336-1d5cdb4a444so17630845ad.1 for ; Tue, 16 Jan 2024 09:03:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1705424587; x=1706029387; darn=lists.postgresql.org; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=4FftUCnYj8QFFM+xN5UIV284ZnYSCk+0aPwo0sypdFA=; b=fOA3UnfR5GwXlZFxVTxrYRXStMvT5xgDFgqL6Tnmyxkg9vDt0kwpGDRme80g1mJAMn JCUObJGBOmHgqr9GzuR+FHuAgDXBwot9dKTLSLVbApmiXe5lvaVFyUYR9N/sj9e6jmc9 pn2CspbZYc08ckazRntwQ24U1/qiox4Nxncsmq58rWXA1AigciCP5LMBfDNPsezz7Eev /hrDOoJ6iS+R2vwhsXS28yWUMWTbdos8JvOvvkYHKtrEpMaNyJa0HD6ybTwk6vSGrAjl 8aM9NRLzuUH8AC0hwR1tNt6WFrk883XbO+2C03bOyC95ggJJC9qHQxqTCpd+sbnG85Si hGTA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705424587; x=1706029387; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=4FftUCnYj8QFFM+xN5UIV284ZnYSCk+0aPwo0sypdFA=; b=R/5rDsUyViJBzLeTb7EZ4nE7pHpOHqbA+T6vjLrtkfzog0CmX5uCz4r6hSgD5uKAPM 03R/1Nj8JKEgpDBpb+iUgxynHC/rzsThN1QEroQow6E/3Kzd0Xoqmf1kXZ5M9eu2fAwt J1ONpAX04gNk75D6/9OQe3xNWhavlk3suNW27pjN33PcWTu4yVjq24PyiNjFoONgAiAQ +rxbZIfDvf+ZJ4otpiWK1BKrBxfD7HYuzioZiZkyOEXr5dEo1W6Hpn+r5tp7Vhy+zkEj Okb90Ql7Qw4nIXYGxMpe/2N2ejdhkbOQH669/DcCwdrou2W0cIXxS/hVLEvKE1xt6Sgc aqIg== X-Gm-Message-State: AOJu0YxyLZ0Mr9bsES6HULF2ThHvkdfRsMCenQq11Mj9eoff8ZEOVeVP LM+6DiGtt4dSIS58ukPhn+TT5BD4m2I= X-Google-Smtp-Source: AGHT+IHAlQ+zkbVsy6zVrGEbtZe7zw0KNPhzUdHxh+pjAYHGM1l46hW9x95mJ8vl99jEP8eb7Rw3eA== X-Received: by 2002:a17:902:f68e:b0:1d4:79b6:101a with SMTP id l14-20020a170902f68e00b001d479b6101amr9783654plg.41.1705424587154; Tue, 16 Jan 2024 09:03:07 -0800 (PST) Received: from [192.168.1.3] (c-76-140-27-218.hsd1.ut.comcast.net. [76.140.27.218]) by smtp.gmail.com with ESMTPSA id kh15-20020a170903064f00b001cf658f20ecsm9559009plb.96.2024.01.16.09.03.06 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 16 Jan 2024 09:03:06 -0800 (PST) Content-Type: multipart/alternative; boundary="------------348HaUTIqYNV7ga38ZtYjeA0" Message-ID: Date: Tue, 16 Jan 2024 10:03:05 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Postgres Database Service Interruption Content-Language: en-CA To: pgsql-general@lists.postgresql.org References: From: Rob Sargent In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------348HaUTIqYNV7ga38ZtYjeA0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 1/16/24 09:29, Bablu Kumar Nayak wrote: > > Dear PostgreSQL Team, > > I am writing to inform you that our PostgreSQL database service is > currently down. We are experiencing an unexpected interruption, and we > are seeking your expertise to help us resolve this issue promptly. > > We would greatly appreciate your immediate attention to this matter. > If there are specific steps we should follow or additional information > you require, please let us know as soon as possible. > > Your assistance in resolving this issue is crucial, and we are > confident in your expertise to help us bring the PostgreSQL database > back online. > Explain your current env. postgres version, how it was install. OS/Version etc What do you see when you "Examine the log output". --------------348HaUTIqYNV7ga38ZtYjeA0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
On 1/16/24 09:29, Bablu Kumar Nayak wrote:

Dear PostgreSQL Team,

 

I am writing to inform you that our PostgreSQL database service is currently down. We are experiencing an unexpected interruption, and we are seeking your expertise to help us resolve this issue promptly.

We would greatly appreciate your immediate attention to this matter. If there are specific steps we should follow or additional information you require, please let us know as soon as possible.

Your assistance in resolving this issue is crucial, and we are confident in your expertise to help us bring the PostgreSQL database back online.

 


Explain your current env. postgres version, how it was install. OS/Version etc
What do you see when you "Examine the log output". 

--------------348HaUTIqYNV7ga38ZtYjeA0--