Re: postgres 9.5 DB corruption
| От | Adrian Klaver |
|---|---|
| Тема | Re: postgres 9.5 DB corruption |
| Дата | |
| Msg-id | 1cd46144-9b6d-499c-b241-e11d8f84c958@aklaver.com обсуждение исходный текст |
| Ответ на | postgres 9.5 DB corruption (Thomas Tignor <tptignor@yahoo.com>) |
| Ответы |
Re: postgres 9.5 DB corruption
|
| Список | pgsql-general |
On 7/24/19 7:38 AM, Thomas Tignor wrote: > Hello postgres community, > > Writing again to see if there are insights on this issue. We have had > infrequent but recurring corruption since upgrading from postgres 9.1 to > postgres 9.5. We are presently on 9.5.16. Our DB-facing app continually > performs a mixture of DML, primarily inserts and updates on two specific > tables, with no single op being suspect. In the past, corruption events > have produced encoding errors on COPY operations (invalid byte sequence > for encoding "UTF8"). More recently, they have caused segmentation > faults. We were able to take a cold backup after a recent event. > SELECTing the corrupted data on our cold backup yields the following > stack. Any info on a solution or how to proceed towards a solution would > be much appreciated. > > Thanks in advance. > In my previous post when I referred to table schema I mean that to include associated schema like triggers, constraints, etc. Basically what is returned by \d in psql. > Tom :-) -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: