Re: dump/restore with a hidden dependency?

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: Chris Curvey <ccurvey(at)zuckergoldberg(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: dump/restore with a hidden dependency?
Date: 2014-08-07 21:59:23
Message-ID: 1407448763.87414.YahooMailNeo@web122302.mail.ne1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Chris Curvey <ccurvey(at)zuckergoldberg(dot)com> wrote:

> Perhaps a pair of triggers?  An insert-or-update trigger on foo, and a
> delete-or-update trigger on bar?

Using a foreign key constraint is best if that can do the right
thing.  If that doesn't work, triggers like you describe are
probably the best option, but you need to cover race conditions.
See this recent post for suggestions:

http://www.postgresql.org/message-id/1406836331.34944.YahooMailNeo@web122303.mail.ne1.yahoo.com

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Peter Geoghegan 2014-08-07 22:10:33 Re: The dangers of streaming across versions of glibc: A cautionary tale
Previous Message Tom Lane 2014-08-07 21:57:29 Re: Re: Feature proposal and discussion: full-fledged column/function equivalence