| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Tweaking Foreign Keys for larger tables |
| Date: | 2014-11-06 22:08:12 |
| Message-ID: | 545BF14C.4020602@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/6/14, 11:49 AM, David G Johnston wrote:
> > Constraint would add a statement-level after trigger for insert,
> > update, delete and trigger, which issues a relcache invalidation if
> > the state was marked valid. Marked as deferrable initially deferred.
> I don't think you'd need to invalidate on insert,
>
>
> Why? Since the FK is not enforced there is no guarantee that what you just inserted is valid
I'm talking about the referenced (aka 'parent') table, not the referring table.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-11-06 22:13:01 | Re: [HACKERS] ltree::text not immutable? |
| Previous Message | Jim Nasby | 2014-11-06 22:03:28 | Re: group locking: incomplete patch, just for discussion |