Re: [PATCH] WIP Add ALWAYS DEFERRED option for constraints

From: Nico Williams <nico(at)cryptonector(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] WIP Add ALWAYS DEFERRED option for constraints
Date: 2017-10-03 21:32:00
Message-ID: 20171003213159.GQ1251@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Tue, Oct 03, 2017 at 02:51:30PM -0500, Nico Williams wrote:
> Anyways, this patch is NOT passing tests at the moment, and I'm not sure
> why. I'm sure I can figure it out, but first I need to understand the
> failures. E.g., I see this sort of difference:
> \d testschema.test_index1
> Index "testschema.test_index1"
> Column | Type | Definition
> --------+--------+------------
> id | bigint | id
> -btree, for table "testschema.test_default_tab"
> +f, for table "testschema.btree", predicate (test_default_tab)
> which means, I think, that I've screwed up in src/bin/psql/describe.c,
> don't it's not obvious to me yet how.

Ah, I needed to adjust references to results columns. I suspect that
something similar relates to other remaining failures.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Maksim Milyutin 2017-10-03 21:36:00 Re: [BUG] Cache invalidation for queries that contains const of temporary composite type
Previous Message Tom Lane 2017-10-03 20:43:06 Re: datetime.h defines like PM conflict with external libraries