public inbox for [email protected]  

help / color / mirror / Atom feed

From: Peter Eisentraut <[email protected]>
To: Bruce Momjian <[email protected]>
Cc: Josh Berkus <[email protected]>
Cc: [email protected]
Subject: Re: Clarification to catalog-pg-class
Date: Fri, 13 Feb 2009 11:13:42 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

Bruce Momjian wrote:
> Peter Eisentraut wrote:
>> Bruce Momjian wrote:
>>> Josh Berkus wrote:
>>>> Bruce,
>>>>
>>>>>> Currently, catalog-pg-class is a bit confusing as to where FKs are 
>>>>>> tracked in pg_class.  Please update the lines for relchecks and 
>>>>>> reltriggers to read:
>>>>>>
>>>>>> relchecks	int2	 	 Number of check constraints on the table (but not 
>>>>>> other types of constraints); see pg_constraint catalog
>>>>> Uh, why do we have to say "but" when we clearly say "check constraints"?
>>>>> Do we need to say "CHECK" contraints?
>>>> Because I've encountered two people on IRC (and a client) who were 
>>>> confused about this, and it confused me briefly when I fielded their 
>>>> questions.  Saying "CHECK constraints" would also probably do it, or 
>>>> saying "check constraints (only)"
>>> Uppercase done, with <literal> tag.
>> This is inconsistent with the rest of the documentation.
> 
> Should I use <emphasis>?  <literal>?

<emphasis> would be appropriate, but I personally don't really buy the 
premise.  If we had to highlight every idiosyncracy in the catalog 
fields, it would end up looking quite colorful.

I suppose a more constructive point would be, where are the other 
constraint types kept track of?

view thread (10+ 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: Clarification to catalog-pg-class
  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