Skip site navigation (1) Skip section navigation (2)

Re: Questions about 9.0 release note

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Questions about 9.0 release note
Date: 2010-03-30 13:23:38
Message-ID: 603c8f071003300623y27500eceo4fda315def6c38f5@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Tue, Mar 30, 2010 at 1:37 AM, Takahiro Itagaki
<itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Dimitri FontaineDate: 2010-03-30 13:36:25
Subject: Re: GSoC
Previous:From: Andrew DunstanDate: 2010-03-30 12:33:03
Subject: keep ppport.h in sync on all branches

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group