Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id F0030B5DC06 for ; Wed, 29 Jun 2011 14:57:10 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 52337-07 for ; Wed, 29 Jun 2011 17:57:04 +0000 (UTC) X-Greylist: delayed 00:25:57.527019 by SQLgrey-1.7.6 Received: from email.wiline.com (email.wiline.com [64.71.12.9]) by mail.postgresql.org (Postfix) with ESMTP id 5AF56B5DBD0 for ; Wed, 29 Jun 2011 14:57:04 -0300 (ADT) Received: from localhost (localhost.localdomain [127.0.0.1]) by email.wiline.com (Postfix) with ESMTP id 6CC8FBD4039; Wed, 29 Jun 2011 13:31:05 -0400 (EDT) X-Virus-Scanned: amavisd-new at wiline.com Received: from email.wiline.com ([127.0.0.1]) by localhost (email.wiline.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id j7WOOqxoZgIs; Wed, 29 Jun 2011 13:31:05 -0400 (EDT) Received: from [192.168.0.104] (c-67-183-65-154.hsd1.wa.comcast.net [67.183.65.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by email.wiline.com (Postfix) with ESMTP id A891CBD4037 for ; Wed, 29 Jun 2011 13:31:04 -0400 (EDT) Message-ID: <4E0B61E6.4020903@wiline.com> Date: Wed, 29 Jun 2011 10:33:26 -0700 From: Dick Wieland Organization: WiLine Networks Inc User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110424 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: pgsql-testers@postgresql.org Subject: v9.1beta2 pg_dumpall error ? (pg_trigger.tgisconstraint) Content-Type: multipart/alternative; boundary="------------030007060500020202010109" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.315 tagged_above=-10 required=5 tests=BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_NJABL_PROXY=2.224, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201106/7 X-Sequence-Number: 248 This is a multi-part message in MIME format. --------------030007060500020202010109 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, I used the v9.1b2 version of pg_dumpall to dump a v8.4.7 database. The resulting dumpfile generated errors when I tried to read it back in under v9.1b2. The complaint is that it's referencing a field in pg_trigger that has been deleted in 9.1 .. CREATE VIEW vtriggers AS SELECT (current_database())::information_schema.sql_identifier AS trigger_catalog, (n.nspname)::information_schema.sql_identifier AS trigger_schema, t.tgenabled, (t.tgname)::information_schema.sql_identifier AS trigger_name, (em.text)::information_schema.character_data AS event_manipulation, (current_database())::information_schema.sql_identifier AS event_object_catalog, (n.nspname)::information_schema.sql_identifier AS event_object_schema, (c.relname)::information_schema.sql_identifier AS event_object_table, (NULL::integer)::information_schema.cardinal_number AS action_order, (NULL::character varying)::information_schema.character_data AS action_condition, ("substring"(pg_get_triggerdef(t.oid), ("position"("substring"(pg_get_triggerdef(t.oid), 48), 'EXECUTE PROCEDURE'::text) + 47)))::information_schema.character_data AS action_statement, (CASE WHEN (((t.tgtype)::integer & 1) = 1) THEN 'ROW'::text ELSE 'STATEMENT'::text END)::information_schema.character_data AS action_orientation, (CASE WHEN (((t.tgtype)::integer & 2) = 2) THEN 'BEFORE'::text ELSE 'AFTER'::text END)::information_schema.character_data AS condition_timing, (NULL::character varying)::information_schema.sql_identifier AS condition_reference_old_table, (NULL::character varying)::information_schema.sql_identifier AS condition_reference_new_table, (NULL::character varying)::information_schema.sql_identifier AS condition_reference_old_row, (NULL::character varying)::information_schema.sql_identifier AS condition_reference_new_row, (NULL::timestamp with time zone)::information_schema.time_stamp AS created FROM pg_namespace n, pg_class c, pg_trigger t, ((SELECT 4, 'INSERT' UNION ALL SELECT 8, 'DELETE') UNION ALL SELECT 16, 'UPDATE') em(num, text) WHERE ((((((n.oid = c.relnamespace) AND (c.oid = t.tgrelid)) AND (((t.tgtype)::integer & em.num) <> 0)) AND (NOT t.tgisconstraint)) AND (NOT pg_is_other_temp_schema(n.oid))) AND (((((pg_has_role(c.relowner, 'USAGE'::text) OR has_table_privilege(c.oid, 'INSERT'::text)) OR has_table_privilege(c.oid, 'UPDATE'::text)) OR has_table_privilege(c.oid, 'DELETE'::text)) OR has_table_privilege(c.oid, 'REFERENCES'::text)) OR has_table_privilege(c.oid, 'TRIGGER'::text))); ERROR: column t.tgisconstraint does not exist at character 1877 Is this expected behavior? It was not a show-stopper, and so far I haven't seen any bad side effects. Thanks, Dick Wieland --------------030007060500020202010109 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi,

I used the v9.1b2 version of pg_dumpall to dump a v8.4.7 database. The resulting dumpfile generated errors when I tried to read it back in under v9.1b2. The complaint is that it's referencing a field in pg_trigger that has been deleted in 9.1 ..

CREATE VIEW vtriggers AS
    SELECT (current_database())::information_schema.sql_identifier AS trigger_catalog, (n.nspname)::information_schema.sql_identifier AS trigger_schema, t.tgenabled, (t.tgname)::information_schema.sql_identifier AS trigger_name, (em.text)::information_schema.character_data AS event_manipulation, (current_database())::information_schema.sql_identifier AS event_object_catalog, (n.nspname)::information_schema.sql_identifier AS event_object_schema, (c.relname)::information_schema.sql_identifier AS event_object_table, (NULL::integer)::information_schema.cardinal_number AS action_order, (NULL::character varying)::information_schema.character_data AS action_condition, ("substring"(pg_get_triggerdef(t.oid), ("position"("substring"(pg_get_triggerdef(t.oid), 48), 'EXECUTE PROCEDURE'::text) + 47)))::information_schema.character_data AS action_statement, (CASE WHEN (((t.tgtype)::integer & 1) = 1) THEN 'ROW'::text ELSE 'STATEMENT'::text END)::information_schema.character_data AS action_orientation, (CASE WHEN (((t.tgtype)::integer & 2) = 2) THEN 'BEFORE'::text ELSE 'AFTER'::text END)::information_schema.character_data AS condition_timing, (NULL::character varying)::information_schema.sql_identifier AS condition_reference_old_table, (NULL::character varying)::information_schema.sql_identifier AS condition_reference_new_table, (NULL::character varying)::information_schema.sql_identifier AS condition_reference_old_row, (NULL::character varying)::information_schema.sql_identifier AS condition_reference_new_row, (NULL::timestamp with time zone)::information_schema.time_stamp AS created FROM pg_namespace n, pg_class c, pg_trigger t, ((SELECT 4, 'INSERT' UNION ALL SELECT 8, 'DELETE') UNION ALL SELECT 16, 'UPDATE') em(num, text) WHERE ((((((n.oid = c.relnamespace) AND (c.oid = t.tgrelid)) AND (((t.tgtype)::integer & em.num) <> 0)) AND (NOT t.tgisconstraint)) AND (NOT pg_is_other_temp_schema(n.oid))) AND (((((pg_has_role(c.relowner, 'USAGE'::text) OR has_table_privilege(c.oid, 'INSERT'::text)) OR has_table_privilege(c.oid, 'UPDATE'::text)) OR has_table_privilege(c.oid, 'DELETE'::text)) OR has_table_privilege(c.oid, 'REFERENCES'::text)) OR has_table_privilege(c.oid, 'TRIGGER'::text)));

ERROR: column t.tgisconstraint does not exist at character 1877


Is this expected behavior? It was not a show-stopper, and so far I haven't seen any bad side effects.

Thanks,
Dick Wieland

--------------030007060500020202010109--