Re: Questions about 9.0 release note - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Questions about 9.0 release note
Date
Msg-id 603c8f071003300623y27500eceo4fda315def6c38f5@mail.gmail.com
Whole thread Raw
In response to Questions about 9.0 release note  (Takahiro Itagaki <itagaki.takahiro@oss.ntt.co.jp>)
Responses Re: [SPAM]Re: Questions about 9.0 release note
List pgsql-hackers
On Tue, Mar 30, 2010 at 1:37 AM, Takahiro Itagaki
<itagaki.takahiro@oss.ntt.co.jp> wrote:
> Hi, I have some questions about 9.0 release note.
> I'd like to work for some of them if required. Comments welcome.
>
> * Allow per-tablespace sequential and random page cost variables
>  (seq_page_cost/(random_page_cost)) via ALTER TABLESPACE ... SET/RESET
>                  ^                ^
> Are those parentheses around random_page_cost intentional?
> They seems to mean just "(seq_page_cost and random_page_cost)".
>
> * EXCLUDE constraints has no tags to be linked.
> The item in release note is pointing the following page,
> http://developer.postgresql.org/pgdocs/postgres/sql-createtable.html#SQL-CREATETABLE-DESCRIPTION
> but the actual description about EXCLUDE constraints are in the subentry
> of "Parameters" section. Can we add a tag to <varlistentry> for EXCLUDE?
>
> * "EXCLUDE constraints" is not indexed from the Index page.
> Should we have for it? Unique Constraints have a section for them:
> http://developer.postgresql.org/pgdocs/postgres/ddl-constraints.html#AEN2431

I think I agree with all of these suggestions.  Also maybe it should
say CREATE TABLE ... CONSTRAINT ... EXCLUDE rather than CREATE TABLE
CONSTRAINT ... EXCLUDE.

...Robert


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: keep ppport.h in sync on all branches
Next
From: Anindya Jyoti Roy
Date:
Subject: Re: GSoC