v9.3.0: bug with pgdump -s? - Mailing list pgsql-general

From Eric B. Ridge
Subject v9.3.0: bug with pgdump -s?
Date
Msg-id 5235D9D9.9070802@tcdi.com
Whole thread Raw
Responses Re: v9.3.0: bug with pgdump -s?  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-general
(Using the new PostgreSQL v9.3.0)

I did a schema-only dump of the 'pg_catalog' schema in the hopes to
study how the built-in OPERATOR CLASSes are defined.

Doing so output a few warnings:

$ [pg930] pg_dump -s -n pg_catalog template1 > /tmp/pg_catalog.sql
pg_dump: WARNING: typtype of data type "any" appears to be invalid
pg_dump: WARNING: typtype of data type "anyarray" appears to be invalid
pg_dump: WARNING: typtype of data type "anyelement" appears to be invalid
pg_dump: WARNING: typtype of data type "anyenum" appears to be invalid
pg_dump: WARNING: typtype of data type "anynonarray" appears to be invalid
pg_dump: WARNING: typtype of data type "anyrange" appears to be invalid
pg_dump: WARNING: typtype of data type "cstring" appears to be invalid
pg_dump: WARNING: typtype of data type "event_trigger" appears to be invalid
pg_dump: WARNING: typtype of data type "fdw_handler" appears to be invalid
pg_dump: WARNING: typtype of data type "internal" appears to be invalid
pg_dump: WARNING: typtype of data type "language_handler" appears to be
invalid
pg_dump: WARNING: typtype of data type "opaque" appears to be invalid
pg_dump: WARNING: typtype of data type "record" appears to be invalid
pg_dump: WARNING: typtype of data type "trigger" appears to be invalid
pg_dump: WARNING: typtype of data type "void" appears to be invalid

Additionally, the operator classes seem to be incomplete in pg_dump's
output:

CREATE OPERATOR CLASS box_ops
     DEFAULT FOR TYPE box USING gist AS
     ;

...

CREATE OPERATOR CLASS text_ops
     DEFAULT FOR TYPE text USING btree AS
     ;

I'd expect them to be fully spec'd with OPERATOR, FUNCTION, and STORAGE
arguments.

Am I expecting too much against 'pg_catalog' or is something bugged?

eric






PROPRIETARY AND COMPANY CONFIDENTIAL COMMUNICATIONS
The information contained in this communication is intended only for
the use of the addressee. Any other use is strictly prohibited.
Please notify the sender if you have received this message in error.
This communication is protected by applicable legal privileges and is
company confidential.



pgsql-general by date:

Previous
From: Robert Nix
Date:
Subject: Segmentation fault: pg_upgrade 9.1 to 9.3: pg_dump: row number 0 is out of range 0..-1
Next
From: Andres Freund
Date:
Subject: Re: v9.3.0: bug with pgdump -s?