Subject: Re: pg_dump restore time and Foreign Keys
From: Simon Riggs <simon@2ndquadrant.com>
To: Robert Treat <xzilla@users.sourceforge.net>
Cc: pgsql-hackers@postgresql.org, Andrew Dunstan <andrew@dunslane.net>
In-Reply-To: <200806071308.00845.xzilla@users.sourceforge.net>
References: <1212647003.19964.19.camel@ebony.site>
	<4847D4A7.70309@dunslane.net> <1212670595.19964.55.camel@ebony.site>
	<200806071308.00845.xzilla@users.sourceforge.net>
Content-Type: text/plain
Date: Sat, 07 Jun 2008 18:41:55 +0100
Message-Id: <1212860515.12046.78.camel@ebony.site>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit


On Sat, 2008-06-07 at 13:08 -0400, Robert Treat wrote:
> On Thursday 05 June 2008 08:56:35 Simon Riggs wrote:
> > On Thu, 2008-06-05 at 07:57 -0400, Andrew Dunstan wrote:

> Heh, I would have argued that the idea should go the other way and
> just make this part of the normal syntax.  Oracle DBA's have been
> doing this for years (MS SQL supports it too actually) and it really
> helps working around having to hold locks on large relations for
> lengthy periods of times. Heck, I'd like to see a no check option for
> all constraints really. 

Interesting that SQL Server does it also.

Holding the lock for a long period is just one more problem. :-)

I'm always torn between the I-know-what-Im-doing-so-give-me-the-option
viewpoint and the some-dumbass-will-abuse-it viewpoint. I see the
results of both viewpoints daily.

Perhaps we need a GUC that says expert_mode = on. In expert_mode we are
allowed to do a range of things that are normally avoided - there would
be an explicit list. Managers can then take a single considered decision
as to whether the situation warrants extreme action and their DBA is
good enough to handle it. That might resolve our continued angst about
whether our users our smart enough to avoid the gotchas, or just smart
enough to win a DBA's Darwin Award. 

The UNIX philosophy has always been to allow the power to exist, yet
seek to minimise the number of people who exercise it. Another idea
might be to make such command options superuser only, to ensure the
power is available, yet only in the hands of, by-definition, the trusted
few.

-- 
 Simon Riggs           www.2ndQuadrant.com
 PostgreSQL Training, Services and Support