Skip site navigation (1) Skip section navigation (2)

Re: Re: Problem with disabling triggers in pg_dump

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
Cc: pgsql-hackers(at)postgresql(dot)org, dyp(at)perchine(dot)com
Subject: Re: Re: Problem with disabling triggers in pg_dump
Date: 2000-07-25 16:23:26
Message-ID: 5433.964542206@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Philip Warner <pjw(at)rhyme(dot)com(dot)au> writes:
>> (Compare the behavior of "tar x" when run as superuser or not.)
>> This has not worked in the past (because those \connect commands can't
>> be ignored), 

> I don't follow...do you mean that psql barfs, or do you mean that there has
> been no way to prevent them being output?

No, I mean that if they're in the script there is no way to have them
be ignored.  There is a way to prevent them from being output (-z switch
to pg_dump, or some such) but *that puts control at the wrong end of the
process*.  When you make a tarfile you don't have to specify whether it
will be restored with the same file ownerships or not; you determine
that when you do the restore.  pg_dump scripts need the same flexibility.

An additional reason for getting rid of the \connect's is performance;
each one causes a fresh backend startup.  You might also care to
contemplate the implications for per-session variables like the "disable
triggers" switch you were suggesting.

>> The thing that really bothers me about this reltriggers hack is that
>> it doesn't work if the script is being run as non-superuser.  I don't
>> see why it's necessary anyway; shouldn't the order of operations be
>> create table;
>> load data;
>> create triggers and indexes;

> Yes, for a full restore that is true. But for a partial restore (where I
> have assumed triggers may exist), it's nice to disable the triggers...

Why is that nice?  If you are loading more data into an existing table
structure, seems to me the *last* thing you'd want is to disable your
consistency checks.  Too risky --- certainly not something I want
pg_dump doing automatically without my knowledge or consent.

I've forgotten the exact details of the scenario that forced us to put
in the reltriggers hack in the first place, but it may well be that
the problem has a better solution now that pg_dump is smart enough to
reorder its output.  I can see from the CVS logs that Jan put the
trigger change into pg_dump on 7-Feb-2000, but I didn't have much luck
finding any related discussion in the mail archives.  Jan, do you recall
the reasoning for it?

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tim DunningtonDate: 2000-07-25 17:15:48
Subject: Re: AW: libpgtcl on aix
Previous:From: Kaare RasmussenDate: 2000-07-25 16:17:44
Subject: Inprise InterBase(R) 6.0 Now Free and Open Source

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group