| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Bablu Kumar Nayak <bablukumarnayak1432(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Postgres Database Service Interruption |
| Date: | 2024-01-16 17:04:05 |
| Message-ID: | 84a11b4c-16c8-45fa-b4e7-cee6d1abf9b0@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 1/16/24 08: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.
I believe you are looking for this:
https://www.postgresql.org/support/professional_support/
>
> HINT: This probably means that some data is corrupted and you will have
> to use the last backup for recovery.
The above being the critical issue.
I'm guessing there was a hardware failure.
> Thanks
> Bablu Nayak
>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dominique Devienne | 2024-01-16 17:04:43 | Re: Moving to Postgresql database |
| Previous Message | Rob Sargent | 2024-01-16 17:03:05 | Re: Postgres Database Service Interruption |