milist ujang writes:
> On Fri, Aug 19, 2022 at 11:02 AM Julien Rouhaud wrote:
>> What it means is that you likely have data corruption. You could try
>> to reindex pg_attribute and see if that fixes that specific problems,
>> but even if it does you will have to investigate how data got
>>
On Fri, Aug 19, 2022 at 11:02 AM Julien Rouhaud wrote:
> Hi,
>
> Please don't top-post on this list (and please trim quoted messages too).
>
>
>
> No, this function is comparing pg_class.relnatts to rows fetched querying
> pg_attribute for the given relation.
>
> any concern if I update
Hi,
Please don't top-post on this list (and please trim quoted messages too).
On Fri, Aug 19, 2022 at 05:55:03AM +0700, milist ujang wrote:
> On Thu, Aug 18, 2022 at 5:33 PM milist ujang wrote:
> >
> > 3rd query ERROR same as subject (ERROR: catalog is missing 3 attribute(s
22 at 5:33 PM milist ujang wrote:
> Hi lists,
>
> I have an index anomaly on a table; getting the error as subject.
>
> dumping queries behind \dS+ of a table, got 4 queries (see detail below)
> 1st query --> OK
> 2nd query --> OK
> 3rd query ERROR same as subject (
Hi lists,
I have an index anomaly on a table; getting the error as subject.
dumping queries behind \dS+ of a table, got 4 queries (see detail below)
1st query --> OK
2nd query --> OK
3rd query ERROR same as subject (ERROR: catalog is missing 3 attribute(s)
for relid 150243)
comment
