| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michel Pelletier <pelletier(dot)michel(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: invalid non-zero objectSubId for object class |
| Date: | 2020-07-10 12:37:54 |
| Message-ID: | 20200710123754.GA12121@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2020-Jul-09, Michel Pelletier wrote:
> I restored a snapshot and I can drop the tables there, so we'll likely
> proceed to swap the replicas over tomorrow. I have this corrupted
> instance i can continue to debug on if necessary. There seem to be some
> other issues now that we're investigating, like a max(timestamp) query on
> the old instance is doing a seqscan on all the partitions instead of using
> an index that's there, the new instance from the snapshot correctly uses
> the index, so I suspect further corruption.
This being RDS makes it very difficult to debug. For example I would
suggest a debugger to find the problem, but you don't have access to
that.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brajendra Pratap Singh | 2020-07-10 13:02:01 | Re: Wal_keep_segment value too high |
| Previous Message | Andreas Kretschmer | 2020-07-10 12:14:48 | Re: Wal_keep_segment value too high |