| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Kumari, Jyoti" <Jyoti(dot)K(at)dell(dot)com> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>, "Tamrakar, Animesh" <Animesh(dot)Tamrakar(at)dell(dot)com>, "Pokharna, Prashant" <Prashant(dot)Pokharna(at)dell(dot)com>, "Bharti, Anand" <Anand(dot)Bharti(at)dell(dot)com> |
| Subject: | Re: Upgrade issue during Postgres 9.6 to 12.3 on the two and more server |
| Date: | 2021-02-26 16:35:36 |
| Message-ID: | 287554.1614357336@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Kumari, Jyoti" <Jyoti(dot)K(at)dell(dot)com> writes:
> connection to database failed: FATAL: could not read block 12 in file "base/1/1259": read only 0 of 8192 bytes.
Looks like your template1 database is corrupt.
I think you could get out of this by dropping template1 and re-creating
it from template0. However, the usual caveats for working with damaged
databases apply: it's a good idea to make a filesystem-level backup of
the entire database directory before you do anything. That way you
can at least get back to where you were if things go further wrong.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-02-26 16:40:13 | Re: BUG #16900: SELECT MAX subquery not allowed in WHERE clause when using WITH RECURSIVE |
| Previous Message | Kumari, Jyoti | 2021-02-26 14:26:16 | Upgrade issue during Postgres 9.6 to 12.3 on the two and more server |