On Fri, Oct 21, 2016 at 4:42 PM, Surinder Kumar <surinder.ku...@enterprisedb.com> wrote: > On Fri, Oct 21, 2016 at 8:52 PM, Dave Page <dp...@pgadmin.org> wrote: >> >> Hi >> >> On Fri, Oct 21, 2016 at 4:16 PM, Surinder Kumar >> <surinder.ku...@enterprisedb.com> wrote: >> > Hi >> > >> > This fix is for exclusion constraint. >> > The options like "order" and "nulls" must be conditional. i.e. include >> > only >> > when access method type is other than "gist". >> >> When creating an index, the asc/desc options are disabled if gist/gin >> used. I think they also should be here. >> >> Also, what about gin indexes in this case? > > As per documentation, > The access method must support amgettuple (see Chapter 52); at present this > means GIN cannot be used
OK, but this patch (unlike the last one) only seems to check for gist. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers
