Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id E445D105A46C for ; Mon, 21 Nov 2011 12:28:14 -0400 (AST) Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RSWj3-000545-DB for pgsql-admin@postgresql.org; Mon, 21 Nov 2011 16:28:13 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id pALGRl2R027173; Mon, 21 Nov 2011 11:27:47 -0500 (EST) To: Rudolf van der Leeden cc: pgsql-admin@postgresql.org, Rudolf van der Leeden Subject: Re: Upgrading DBs with type=citext from 9.0.5 to 9.1.1 using pg_upgrade and create extension In-reply-to: <9017.1321887060@sss.pgh.pa.us> References: <42DFCA4F-34A9-4265-9A99-A45E45021FFA@logicunited.com> <9017.1321887060@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Mon, 21 Nov 2011 09:51:00 -0500" Date: Mon, 21 Nov 2011 11:27:46 -0500 Message-ID: <27172.1321892866@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 201111/106 X-Sequence-Number: 38700 I wrote: > Rudolf van der Leeden writes: >> we are running into a problem with the following upgrade scenario: > Hmm. I think the citext update script is missing a couple of things. This patch seems to fix the case for me: http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=94bdb198813b079467d7ed07c6f72ac896da7161 If you have an already-upgraded database, you can just run the additional commands by hand. regards, tom lane