Re: [HACKERS] System Catalogs

From: Bernard Frankpitt <frankpit(at)pop(dot)dn(dot)net>
To: Chris Bitmead <chris(dot)bitmead(at)bigfoot(dot)com>, pgsql-hackers(at)hub(dot)org
Subject: Re: [HACKERS] System Catalogs
Date: 1999-05-14 13:37:44
Message-ID: 373C2728.9574D9AA@pop.dn.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I found that the best way to figure out the system catalogs was to do
the following steps

(i) Stare at the diagram in the html web pages until you are cross-eyed.

(ii) Look through the .h files in src/include/catalogs/ realising of
course that many of the fields/attributes that are defined are not used.

(iii) Use the \t command in a test database to inspect the actual
tables,
and try doing a bunch of SELECT queries with joins across catalogs to
figure out the relational structure (Schema).

Seriously, its not that bad once you get into the groove.

One interesting feature that I stumbled on was that at least one of the
methods that is required for the definition of indices requires more
than
8 arguments, the maximum number for a poastgres function if it is
entered with a CREATE FUNCTION command. This means that if you wish to
dynamically load a new type of index you have to use INSERT INTO
pg_proc commands to enter the index methods straight into the catalog
table.

Bernie

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 1999-05-14 14:38:34 Re: [HACKERS] CVS
Previous Message Thomas Lockhart 1999-05-14 13:32:57 Re: [HACKERS] CVS