Re: pg_get_constraintdef() doesn't always give an equal constraint

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jon Jensen <jon(at)endpoint(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: pg_get_constraintdef() doesn't always give an equal constraint
Date: 2015-05-21 23:01:38
Message-ID: 20150521230137.GD26667@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> Stephen Frost <sfrost(at)snowman(dot)net> writes:
> > * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> >> It's interesting to consider something like the COPY_PARSE_PLAN_TREES
> >> #define, which inserts code into the backend to see whether copyfuncs.c
> >> and equalfuncs.c are sane or not. Running the regression tests with
> >> that turned on provides pretty thorough coverage of those modules.
>
> > Do we have any buildfarm members which are running with that? If not,
> > would anyone object to doing so?
>
> Yeah, it would be a fine idea to have a critter or two using that.

Apologies for not having gotten to this, and thanks for setting one up.

Stephen

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Venkata Balaji N 2015-05-22 00:02:18 Re: BUG #13324: Database returing incorrect results on querying slect clause
Previous Message Michael Paquier 2015-05-21 22:43:36 Re: unrecognized option '--help