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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephen Frost <sfrost(at)snowman(dot)net>
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-03-30 15:02:31
Message-ID: 14670.1427727751@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jon Jensen 2015-03-30 16:13:58 Re: pg_get_constraintdef() doesn't always give an equal constraint
Previous Message Stephen Frost 2015-03-30 15:00:37 Re: pg_get_constraintdef() doesn't always give an equal constraint