Search Postgresql Archives
Re: Possible corrupt index?
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
Subject
: Re: Possible corrupt index?
From
: Michael Lewis <mlewis@xxxxxxxxxxx>
Date
: Tue, 16 Apr 2019 11:05:51 -0600
Cc
: "pgsql-general@xxxxxxxxxxxxxxxxxxxx" <pgsql-general@xxxxxxxxxxxxxxxxxxxx>
In-reply-to
: <
AM0PR06MB4004A8622A0B0ABF2355D771A7240@AM0PR06MB4004.eurprd06.prod.outlook.com
>
References
: <
AM0PR06MB4004A8622A0B0ABF2355D771A7240@AM0PR06MB4004.eurprd06.prod.outlook.com
>
Which version? What are the queries you are running which give unexpected behavior? Have your run explain analyze on those to check what plan is being used? Have your reindexed all or only the one you suspect?
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
Follow-Ups
:
RE: Possible corrupt index?
From:
Zahir Lalani
References
:
Possible corrupt index?
From:
Zahir Lalani
Prev by Date:
Re: Alter domain type / avoiding table rewrite
Next by Date:
Re: Possible corrupt index?
Previous by thread:
Possible corrupt index?
Next by thread:
RE: Possible corrupt index?
Index(es):
Date
Thread
[Index of Archives]
[Postgresql Jobs]
[Postgresql Admin]
[Postgresql Performance]
[Linux Clusters]
[PHP Home]
[PHP on Windows]
[Kernel Newbies]
[PHP Classes]
[PHP Books]
[PHP Databases]
[Postgresql & PHP]
[Yosemite]