Re: Catalog insertion

From: Carmen Martinez <carmenmtezcruz(at)yahoo(dot)es>
To: Peter Childs <peterachilds(at)gmail(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Catalog insertion
Date: 2007-07-10 11:06:25
Message-ID: 20070710110625.20556.qmail@web26506.mail.ukl.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

I'd like to use the same system we did with oracle due all the rdbms use a catalog in order to store their system tables and structures.
Using the CREATE TYPE sentence implies a new implementation totally different from the previous one.

Peter Childs <peterachilds(at)gmail(dot)com> escribió:

On 10/07/07, Carmen Martinez <carmenmtezcruz(at)yahoo(dot)es> wrote:
I know all you say, but we actually are trying to extend the postresql with new data types, and they must be theorically in the system catalog. Also, these new data types go with some functions for manage it.

We have also implemented this in Oracle and now we want to do this with postgresql.

Any idea it would be welcome. But if this possibility is disallowed by policy, and I use the database as a server, how can I solve it?. Do I have to disallowed all conexions and then do these tasks in the server?.

Ahh, I am working in windows so please take it into account!.

"Create type" I think might be what you need then.

see http://www.postgresql.org/docs/8.2/static/sql-createtype.html

Peter.

Thank you very much
Carmen.

Alvaro Herrera < alvherre(at)commandprompt(dot)com> escribió: Carmen Martinez escribió:
> I want to insert new tables in the pg_catalog schema. So I have to
> execute a common create table sentence like "Create Table
> pg_catalog.newTable ....", but I am not allowed to do that and I do
> not know why.
>
> Following I show one of the sentences I execute and the error messages
>
>
> One of the tables I try to create is:
>
> CREATE TABLE pg_catalog.COL_LIST ( OBJ OID NOT NULL, COL OID NOT NULL,
> T_TYPE numeric(1) NOT NULL, LEN numeric(2) NOT NULL, COM
> varchar(100) , PRIMARY KEY (OBJ, COL) , CONSTRAINT
> LEN_TOO_LONG_IN_COL_LIST CHECK (LEN>=1 AND LEN<=10), CONSTRAINT
> TYPE_MUST_BE_1_2_o_3 CHECK (T_TYPE=1 OR T_TYPE=2 OR T_TYPE=3))
>
> ERROR: permission denied to create "pg_catalog.col_list"
> DETAIL: System catalog modifications are currently disallowed.

Oh, you can't do that. It's disallowed by policy. If you want to
create catalogs you need to be in standalone or bootstrap mode
(typically they are created by declaring a src/include/catalog/*.h file
and having it be included in postgres.bki by the genbki script).

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

---------------------------------

LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com


---------------------------------

LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Alvaro Herrera 2007-07-10 13:21:14 Re: Catalog insertion
Previous Message Stephen Frost 2007-07-10 10:14:56 Re: local kerberos authentication?