Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 55A44633107 for ; Mon, 16 Feb 2009 16:44:15 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 88612-06 for ; Mon, 16 Feb 2009 16:44:08 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.27]) by mail.postgresql.org (Postfix) with ESMTP id BF9A66330D7 for ; Mon, 16 Feb 2009 16:44:06 -0400 (AST) Received: by qw-out-2122.google.com with SMTP id 5so569707qwd.61 for ; Mon, 16 Feb 2009 12:44:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=3xjsngl3N8USuI7YqseEG/nspmMuET0EcjyGoHmUZt0=; b=IT2dXpHloUAKx28USnoAFf7YOZZDDIsLYhdpSl/qEaPs1Wn9tsDCoTugAEenL5KXn9 sU82Y1fZLx5xzJWxwMECyf4BmdNJFIIEP758ksbTJEWevXsJKbKuoIB8+8G9MQFkS+F6 VY+FzIWUFQPz8M71b7MThpPEP5Kl/n4dGFj/8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=Gzx6QtrbEFSpuNZ+2TZ0r05yDr8sdmI5Q2izd1KUjIA2pZUNgX0KtHzlRJT72pB1P1 R6XmuqsdGlvHS+um5NA0O7XSMAsgcz9JfPtO2ide5SNKcj8hOkD4e3YlhsvYqLXyy+D/ loiY35r7H9KxMkYTrWYE1R2dTL7FH5BCTU8/E= MIME-Version: 1.0 Received: by 10.224.20.12 with SMTP id d12mr8782500qab.32.1234817045613; Mon, 16 Feb 2009 12:44:05 -0800 (PST) Date: Tue, 17 Feb 2009 02:14:05 +0530 Message-ID: Subject: tsearch2 migration 8.2 --> 8.3 From: Rajesh Kumar Mallah To: postgres admin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200902/107 X-Sequence-Number: 31328 Hi, I am attempting to migrate 8.2 database to 8.3 database , the database uses tsearch2. The contrib module tsearch2 that is supposed to provide backward compatibility is also installed. It has been observed that inspite of install the contrib module some functions referred in the 8.2 dump is neither provided by the core nor the contrib. Eg CREATE FUNCTION gtsq_in(cstring) RETURNS gtsq AS '$libdir/tsearch2', 'gtsq_in' LANGUAGE c STRICT; ERROR: could not find function "gtsq_in" in file "/usr/local/pgsql/lib/tsearch2.so" ALTER FUNCTION public.gtsq_in(cstring) OWNER TO postgres; ERROR: function public.gtsq_in(cstring) does not exist CREATE FUNCTION gtsq_out(gtsq) RETURNS cstring AS '$libdir/tsearch2', 'gtsq_out' LANGUAGE c STRICT; ERROR: could not find function "gtsq_out" in file "/usr/local/pgsql/lib/tsearch2.so" ALTER FUNCTION public.gtsq_out(gtsq) OWNER TO postgres; ERROR: function public.gtsq_out(gtsq) does not exist On attempting to delete the type that uses these in/out functions it is observed that they do not touch in table columns or indexes. eg bric=# begin work; drop type gtsq cascade; rollback; BEGIN NOTICE: drop cascades to function gtsq_in(cstring) NOTICE: drop cascades to function gtsq_out(gtsq) NOTICE: drop cascades to function gtsq_consistent(gtsq,internal,integer) NOTICE: drop cascades to operator class gist_tp_tsquery_ops for access method gist NOTICE: drop cascades to function gtsq_same(gtsq,gtsq,internal) DROP TYPE ROLLBACK My Question is is it safe to drop that type and migrate ? Regds mallah