public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tom Lane <[email protected]>
To: Clément Prévost <[email protected]>
Cc: [email protected]
Cc: Peter Eisentraut <[email protected]>
Subject: Re: Documentation on information_ schema columns that does not exist
Date: Sun, 31 May 2015 17:54:44 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CABaKae8+p6=zhCM=Qrq_GMN88pFqjb5EgHpy9bjGaKZfvJmzZA@mail.gmail.com>
References: <CABaKae8+p6=zhCM=Qrq_GMN88pFqjb5EgHpy9bjGaKZfvJmzZA@mail.gmail.com>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-docs>
=?UTF-8?B?Q2zDqW1lbnQgUHLDqXZvc3Q=?= <[email protected]> writes:
> I found out that the following columns are documented (9.1->9.4) but not
> present in the information_schema table of my 9.4 instance (ubuntu):
> * information_schema.foreign_table_options.foreign_server_catalog
> * information_schema.foreign_table_options.foreign_server_name
Yeah, that does seem like a copy-and-pasteo; there should only be 5
columns in the view according to the SQL standard and our code.
Another problem in the same area is that the column types of
foreign_table_schema and foreign_table_name seem to be "name":
# \d *.foreign_table_options
View "information_schema.foreign_table_options"
Column | Type | Modifiers
-----------------------+-----------------------------------+-----------
foreign_table_catalog | information_schema.sql_identifier |
foreign_table_schema | name |
foreign_table_name | name |
option_name | information_schema.sql_identifier |
option_value | information_schema.character_data |
The documentation claims these should be sql_identifier, and that's
what I'd expect in a SQL-standard view ...
regards, tom lane
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
view thread (9+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Documentation on information_ schema columns that does not exist
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox