From: Tom Lane <tgl@sss.pgh.pa.us>
To: Adam Brusselback <adambrusselback@gmail.com>
cc: pgsql-performance@postgresql.org
Subject: Re: GIN index not used if created in the same transaction as query
In-reply-to: 
 <CAMjNa7e-Q9DwX4TZqtuQNkitf0b0W65NsW54u7HLnMU+m2pbkw@mail.gmail.com>
References: 
 <CAMjNa7c_=5pZL8T-kBhiRb0=an=DbpGg5jsYZ9guDs8i75jwcg@mail.gmail.com>
 <31274.1495208001@sss.pgh.pa.us>
 <CAMjNa7e-Q9DwX4TZqtuQNkitf0b0W65NsW54u7HLnMU+m2pbkw@mail.gmail.com>
Comments: In-reply-to Adam Brusselback <adambrusselback@gmail.com>
	message dated "Fri, 19 May 2017 11:49:32 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <436.1495210198.1@sss.pgh.pa.us>
Date: Fri, 19 May 2017 12:09:58 -0400
Message-ID: <437.1495210198@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

Adam Brusselback <adambrusselback@gmail.com> writes:
> Is there any easy way I can know if an index is usable or not? Are there
> any catalog views or anything I could check that in?

IIRC, you can look at pg_index.indcheckxmin --- if that's set, then
the index had broken HOT chains during creation and may not be usable
right away.  Telling whether your own transaction can use it is harder
from SQL level, but if you're in the same transaction that made the
index then the answer is probably always "no" :-(

			regards, tom lane


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance