Skip site navigation (1) Skip section navigation (2)

RE: Raw constraint & pg_relcheck.rcsrc

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-hackers" <pgsql-hackers(at)postgreSQL(dot)org>
Subject: RE: Raw constraint & pg_relcheck.rcsrc
Date: 2000-08-03 05:36:53
Message-ID: 001201bffd0c$d4a548e0$2801007e@tpf.co.jp (view raw or flat)
Thread:
Lists: pgsql-hackers
> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> 
> "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> writes:
> > Is pg_relcheck.rcsrc equivalent to the original raw constraint ?
> 
> To the best of deparse_expression()'s ability, it should be.
> I'm not real sure why we bother to store it, rather than deparsing
> rcbin on-the-fly on demand...
>

I'm looking at DefineRelation() in commands/creartinh.c.
In case of inheritance,constraints of super classes are
stored using their pg_relcheck.rcbin-s. It seems bad 
in case of multiple inheritance.  rcsrc-s may be available
instead.

Comments ?  

Regards.

Hiroshi Inoue
Inoue(at)tpf(dot)co(dot)jp

In response to

pgsql-hackers by date

Next:From: Magnus HaganderDate: 2000-08-03 08:15:20
Subject: RE: comparing rows
Previous:From: Tom LaneDate: 2000-08-03 05:07:26
Subject: Re: Raw constraint & pg_relcheck.rcsrc

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group