st 19. 12. 2018 v 19:01 odesílatel Tom Lane napsal:
> Pavel Stehule writes:
> > st 19. 12. 2018 v 17:59 odesílatel Tom Lane napsal:
> >> So either this is something we fixed since 9.5.5, or your summary
> >> of the problem is missing many critical details.
>
> > I got different error message "c
Pavel Stehule writes:
> st 19. 12. 2018 v 17:59 odesílatel Tom Lane napsal:
>> So either this is something we fixed since 9.5.5, or your summary
>> of the problem is missing many critical details.
> I got different error message "could not open critical system index". I
> checked files, and rela
st 19. 12. 2018 v 17:59 odesílatel Tom Lane napsal:
> Pavel Stehule writes:
> > some customer has PostgreSQL 9.5.5. He cannot to login to database due
> > broken index
> > When I use single mode against to this database I got a error
> > start transaction
> > could not open critical system index
st 19. 12. 2018 v 18:07 odesílatel Alvaro Herrera
napsal:
> On 2018-Dec-19, Tom Lane wrote:
>
> > Pavel Stehule writes:
> > > some customer has PostgreSQL 9.5.5. He cannot to login to database due
> > > broken index
> > > When I use single mode against to this database I got a error
> > > start
On 2018-Dec-19, Tom Lane wrote:
> Pavel Stehule writes:
> > some customer has PostgreSQL 9.5.5. He cannot to login to database due
> > broken index
> > When I use single mode against to this database I got a error
> > start transaction
> > could not open critical system index 2679
>
> I can't re
Pavel Stehule writes:
> some customer has PostgreSQL 9.5.5. He cannot to login to database due
> broken index
> When I use single mode against to this database I got a error
> start transaction
> could not open critical system index 2679
I can't reproduce this. Removing file 2679 (pg_index_index
Hi
some customer has PostgreSQL 9.5.5. He cannot to login to database due
broken index
When I use single mode against to this database I got a error
start transaction
could not open critical system index 2679
Unfortunately option -E doesn't show anything
Regards
Pavel