public inbox for [email protected]  

help / color / mirror / Atom feed

From: Josh Berkus <[email protected]>
To: Bruce Momjian <[email protected]>
Cc: [email protected]
Subject: Re: Clarification to catalog-pg-class
Date: Sat, 07 Feb 2009 11:04:50 -0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

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)"

BTW, why do we still have relukeys etc. around?  If we haven't used them 
in 5 versions, shouldn't we purge them?

> 
>> reltriggers	int2	 	Number of triggers on the table, including 
>> constraint-triggers for foreign keys; see pg_trigger catalog
> 
> pg_class doesn't have that column anymore, it has relhastriggers.

Ah.  Where are we tracking FKs at this point, then?

--Josh

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]
  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