| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Alexander Kass <alexander(dot)kass(at)jetbrains(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: No xmin in pg_database |
| Date: | 2021-09-02 10:41:43 |
| Message-ID: | 2241619.1630579303@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
> On Thu, 2021-09-02 at 08:50 +0300, Alexander Kass wrote:
>> We have a small number of users that do not have xmin in pg_database
>> (we've asked them to try `select xmin from pg_database` and got
>> `column xmin does not exist`).
> All PostgreSQL tables have "xmin", and all catalog tables do as well.
Indeed. This seems to be evidence of corruption in the pg_attribute
catalog. If you're really lucky, reindexing pg_attribute might fix
it, though I wonder what other problems there are. (It's odd though
that identical corruption would happen to different installations.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | balasubramanian c r | 2021-09-02 11:09:09 | Querying a table with jaccard similarity with 1.6 million records take 12 seconds |
| Previous Message | Alexander Kass | 2021-09-02 09:10:10 | Re: No xmin in pg_database |