Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bn2q4-0006oA-8j for pgsql-admin@arkaria.postgresql.org; Thu, 22 Sep 2016 12:10:52 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bn2q3-0005Wb-NG for pgsql-admin@arkaria.postgresql.org; Thu, 22 Sep 2016 12:10:51 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bn2oM-0003at-Gp for pgsql-admin@postgresql.org; Thu, 22 Sep 2016 12:09:06 +0000 Received: from mail-vk0-x232.google.com ([2607:f8b0:400c:c05::232]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bn2oJ-0000nz-UA for pgsql-admin@postgresql.org; Thu, 22 Sep 2016 12:09:05 +0000 Received: by mail-vk0-x232.google.com with SMTP id 192so21690525vkl.0 for ; Thu, 22 Sep 2016 05:09:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=avast-com.20150623.gappssmtp.com; s=20150623; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-transfer-encoding; bh=9eXwu4BPen9Q46QLaInaYUS4WcUBK+DHqnr716h1m6c=; b=DW88BrVhQgSeJZWMpuF7RL8m69PXVQ50TPg/V+0WhRv/ilF14zUdxUQe7Zu6XYjnut 1dreWkiQAvVAp6FDJMA1mO/8rVEemtNDn4oKoYGQz1vTI/K1W9nlYaUaGkahzWwPTK4D VULzEHQPy/L09Jgq8PonDOH4CMlxcUwbgEmo0dznw3XOQnLWAyn3ZTiQZRG/W9E5BxYq gRZvCGGzUrbZ36sUS278WiHuVahBI6dunahFsk5VQkGf0pTHWO4+ywEY/tguHYQU5+6w curqngvrOkyIDsvy91jHBsBiBJFHWcIWgAerGdE57GHcC6oETlfZY0VGKSLmOAHdH13G J2BA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc :content-transfer-encoding; bh=9eXwu4BPen9Q46QLaInaYUS4WcUBK+DHqnr716h1m6c=; b=TA2nh7FtvuOjm+FV9C8CNfl9AhPxUXk+GZ9xda6uHFZqeN2KOVpS/ZAIyuiZgNnaQ1 yGk+Hr2DwIlPOPhAM6YUFT8r5A55Jfzxw9VploSB10sscqhhJCC9fJ2kcnlbKnjOxLPn zsgzGWMRsq4dwwFzVRV0U00yg44Bc9kU21/ssb3yDRSJckz5e3XU+BQtZgty7M4R99nJ 3ogFVEsalAASjgkgUFm1QRuwH511F+xKzyHQUv5bCrq4POqchg7Ciw9qCKW1lotpGQdD d+xV1snLxJ9HJEVCspppFHYH0xEYiTUIrdRugBeU+P0akEwmEW8q3mC1I34r41JLxAb3 Yz7Q== X-Gm-Message-State: AE9vXwOXAq3CfhrccKzIivvIU1K5tAOL133Ve5YXDPqUTQDcIafJyXtdAZdKYrsBtjKnrncCq0czlDHCwtvSeUXn X-Received: by 10.31.152.20 with SMTP id a20mr1391408vke.123.1474546142574; Thu, 22 Sep 2016 05:09:02 -0700 (PDT) From: =?UTF-8?B?VG9tw6HFoSBVa28=?= References: <05172a3859cb6805b368084dfd015dbc@mail.gmail.com> <14201.1474544219@sss.pgh.pa.us> In-Reply-To: <14201.1474544219@sss.pgh.pa.us> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQJeZc6q4p7G23ZWufj/ZOJoeizsWAJCsalDAuAQpvIDTWZHGwFoetKunx4DCmA= Date: Thu, 22 Sep 2016 14:09:01 +0200 Message-ID: <4017414da2205610f2f2a6762b145f23@mail.gmail.com> Subject: Re: Problem with extension To: Tom Lane Cc: pgsql-admin@postgresql.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Hi Tom, It worked! XY=3D# create extension hstore from unpackaged; CREATE EXTENSION XY=3D# \dx List of installed extensions Name | Version | Schema | Description -------------+---------+------------+--------------------------------------= ------------ adminpack | 1.0 | pg_catalog | administrative functions for PostgreSQL hll | 1.0 | public | type for storing hyperloglog data hstore | 1.2 | public | data type for storing sets of (key, value) pairs pgstattuple | 1.0 | public | show tuple-level statistics plpgsql | 1.0 | pg_catalog | PL/pgSQL procedural language (5 rows) Thanks for help. T. -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: Thursday, September 22, 2016 1:37 PM To: Tom=C3=A1=C5=A1 Uko Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] Problem with extension =3D?UTF-8?B?VG9tw6HFoSBVa28=3D?=3D writes: > Recreating extension again via =E2=80=9ECREATE EXTENSION=E2=80=9C doesn= =E2=80=99t work XY=3D# > CREATE EXTENSION hstore SCHEMA public; > ERROR: type "hstore" already exists > XY=3D# CREATE EXTENSION hstore; > ERROR: type "hstore" already exists Perhaps what you've got there is an hstore installation from before extensions existed? Try "create extension hstore from unpackaged" to update it. > Another thing, when we try to add extesion with insert to pg_extension > it gets OID far greater than any other: > XY=3D# select *,pg_extension.oid from pg_extension; When you don't know what you are doing, trying to fix it with manual surgery on the system catalogs is a good way to make things worse. regards, tom lane --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin