| From: | Rod Taylor <rbt(at)rbt(dot)ca> |
|---|---|
| To: | Thusitha Maheepala <thusitha(at)onsys(dot)com(dot)au> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Postgredb issue |
| Date: | 2020-05-09 15:05:58 |
| Message-ID: | CAHz80e54q_BuxxnK8z-9fhdJVz9dR+VQ6tU1CX0h=Ma2BD-sdw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sat, 9 May 2020 at 09:18, Thusitha Maheepala <thusitha(at)onsys(dot)com(dot)au>
wrote:
> Hi Team,
> I need big support in my postgresql server suddenly shutdown.But
> again didn't start I attached here with log can you give solution i search
> community also i didn't find solution.I attached here with log.can you give
> solution for me.Fix this issue.I really appericate,
>
>
It appears all errors are related to the c_acctprocessorlog_pkey index? Run
the below to ditch the current index and rebuild with data from the table
files.
REINDEX INDEX c_acctprocessorlog_pkey;
It could be a bug in Pg but it's most likely a filesystem corruption or a
hardware issue (bad memory, bad disk controller, bad disk itself). You
might find some additional useful messages in the kernel logs.
Since you don't mention a version, upgrade to the most recent minor version
of Pg very soon.
regards,
Rod
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rod Taylor | 2020-05-09 15:09:10 | Re: Postgredb issue |
| Previous Message | David G. Johnston | 2020-05-09 14:38:00 | Re: Postgredb issue |