Patch applied (once Murtuza showed me how to recreate the problem). Thanks!
On Mon, Jan 9, 2017 at 2:42 PM, Dave Page <dp...@pgadmin.org> wrote: > Hi > > On Mon, Jan 9, 2017 at 10:46 AM, Murtuza Zabuawala > <murtuza.zabuaw...@enterprisedb.com> wrote: >> Hi Dave, >> >> I followed, >> >> 1) First click on main properties panel. >> >> 2) Sample definition, >> >> CREATE TABLE public.test_table >> ( >> id character varying(3) COLLATE pg_catalog."default" NOT NULL, >> col1 bigint, >> CONSTRAINT test_pkey PRIMARY KEY (id) >> ) >> WITH ( >> OIDS = FALSE >> ) >> TABLESPACE pg_default; >> >> With above created table, create exclusion constraint with following options >> using GUI, >> >> ALTER TABLE public.test_table >> ADD CONSTRAINT test_exclu EXCLUDE USING btree ( >> col1 DESC NULLS LAST WITH =); >> >> Click on Save, Exclusion constraint will be created successfully but you >> will get error as wrong OID was sent while generating node info. > > Nope - it works fine for me. I wonder what's different... > > > > -- > Dave Page > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake > > EnterpriseDB UK: http://www.enterprisedb.com > The Enterprise PostgreSQL Company -- 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
