Received: from maia.hub.org (maia-2.hub.org [200.46.204.251])
	by mail.postgresql.org (Postfix) with ESMTP id C3E72B5DBDE
	for <pgsql-docs-postgresql.org@mail.postgresql.org>;
	Thu, 19 May 2011 17:19:20 -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 52066-01 for
	<pgsql-docs-postgresql.org@mail.postgresql.org>;
	Thu, 19 May 2011 20:19:13 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-gy0-f174.google.com (mail-gy0-f174.google.com
	[209.85.160.174])
	by mail.postgresql.org (Postfix) with ESMTP id EEE1BB5DBC1
	for <pgsql-docs@postgresql.org>; Thu, 19 May 2011 17:19:12 -0300 (ADT)
Received: by gyd10 with SMTP id 10so1070380gyd.19
	for <pgsql-docs@postgresql.org>; Thu, 19 May 2011 13:19:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:cc:content-type
	:content-transfer-encoding;
	bh=P9A439tESJ4v7rAMBbQvd2BZ3KNcBXcI22T3qPtIdPE=;
	b=LM/qfLgu1cGFRcSHfQcjsFnAhQP9nTzojmbFho+jWv/SpwyrAPWTeR4yhZDqjqhPjG
	lwxngnroDWlrkM+XGkxg22k38Y/yq50URsrc2AHC9LjVzcSw3Ntnitm3BIj1w7gKi3i4
	+tGLyGabS+DT7maYLdk4Z3mOfAo6N/3U+7ydg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	b=vhYQH8oGmHRXCchWYFVAPEZtHCbXCt0AudinZQoJPUtuGFF6nvZurl205byXhJEVed
	HmlWVV687dh/DoFdmUO0+xNzcRBZnnblQlh7nW+7C8IVvyzcHXBDZPdyKbKSuN/i7Uct
	45KyEurRa29b/ykZgnq6pxEz+DUFPXexffTuk=
MIME-Version: 1.0
Received: by 10.236.135.132 with SMTP id u4mr4336794yhi.340.1305836351977;
	Thu, 19 May 2011 13:19:11 -0700 (PDT)
Received: by 10.236.105.180 with HTTP; Thu, 19 May 2011 13:19:11 -0700 (PDT)
In-Reply-To: <BANLkTi=wObY6Wnn3PLoCezT5EZdjeubROw@mail.gmail.com>
References: <BANLkTikx0iKbcU4pPAMDPXcL1c4fX6nWMQ@mail.gmail.com>
	<BANLkTi=wObY6Wnn3PLoCezT5EZdjeubROw@mail.gmail.com>
Date: Thu, 19 May 2011 16:19:11 -0400
Message-ID: <BANLkTim8zRxa0=DRSQZ26Fqd2SmOdmP-AQ@mail.gmail.com>
Subject: Re: ALTER TABLE doc small thing
From: Robert Haas <robertmhaas@gmail.com>
To: Grzegorz Szpetkowski <gszpetkowski@gmail.com>
Cc: pgsql-docs@postgresql.org
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.898 tagged_above=-5 required=5 tests=BAYES_00=-1.9,
	FREEMAIL_FROM=0.001, RFC_ABUSE_POST=0.001
X-Spam-Level: 
X-Archive-Number: 201105/58
X-Sequence-Number: 6733

On Mon, May 9, 2011 at 2:12 PM, Grzegorz Szpetkowski
<gszpetkowski@gmail.com> wrote:
> "NOTE 30 =97 If MATCH FULL or MATCH PARTIAL is specified for a
> referential constraint and if the referencing table has only one
> column specified in <referential constraint definition> for that
> referential constraint, or if the referencing table has more than one
> specified column for that <referential constraint definition>, but
> none of those columns is nullable, then the effect is the same as if
> no
> <match type> were specified."
>
> I found that in SQL:2003 draft, so in above case MATCH FULL is
> syntactically ok, but rather confusing and effectively do nothing
> (maybe just impression purpose).

I guess we could remove it, but I don't think it's really doing any harm.

--=20
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company