| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | dyuzenn98(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18099: ERROR: could not access status of transaction 4007513275 |
| Date: | 2023-09-08 17:45:17 |
| Message-ID: | 82730b0204b4daaa924d031479af86c11bd7801f.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, 2023-09-08 at 06:36 +0000, PG Bug reporting form wrote:
> The following bug has been logged on the website:
>
> Bug reference: 18099
> Logged by: Dogukan Yuzen
> Email address: dyuzenn98(at)gmail(dot)com
> PostgreSQL version: 14.8
> Operating system: Red Hat Enterprise Linux Server release 7.9 (Maipo
> Description:
>
> A few days ago , we had some problems in our production database.
> We can't read the table.
>
> We can't solve this problem.
> ERROR: could not access status of transaction 4007513275
> DETAIL: Could not open file "pg_xact/0EED": No such file or directory.
That's data corruption. Restore your backup.
What is your proof that this was caused by a PostgreSQL software bug?
More frequent causes are hardware problems or pilot error (pg_resetwal
or other manipulations that break your database).
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2023-09-08 21:10:51 | Re: About #13489, array dimensions and CREATE TABLE ... LIKE |
| Previous Message | Tom Lane | 2023-09-08 16:08:19 | Re: BUG #18097: Immutable expression not allowed in generated at |