Re: Instructions for adding new catalog

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Gustavo Tonini" <gustavotonini(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Instructions for adding new catalog
Date: 2008-08-04 03:04:12
Message-ID: 19575.1217819052@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Gustavo Tonini" <gustavotonini(at)gmail(dot)com> writes:
> Well, just for documenting the process...
> Adding new postgres catalog in 2 little steps:

> 1)Write catalog header file and save it into "src/include/catalog"
> directory. Hint: copy format from other catalog headers.
> 2)Add your header file name to variable POSTGRES_BKI_SRCS in file
> "src/backend/catalog/Makefile"

As long as we're documenting ...

* Documenting a new catalog in catalogs.sgml is not considered optional.
* Most likely, your catalog needs some indexes, which should be declared
in catalog/indexing.h.
* Of course, the reason you are defining a new system catalog is that
the C code is going to know about it. So there is a whole lot of
other stuff you probably need to write: object insertion code,
object deletion code, lookup code (maybe a new syscache or two).
Traditionally the lowest-level insertion/deletion code goes into
catalog/pg_yourcatalog.c, while slightly higher-level code such as
the implementation of new utility commands to manage this new kind
of object will go elsewhere.

That's before you get to any actual new functionality...

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Sushant Sinha 2008-08-04 03:57:11 Re: small bug in hlCover
Previous Message Robert Treat 2008-08-04 02:57:55 Re: Mini improvement: statement_cost_limit