From: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: disable triggers using psql |
Date: | 2011-02-17 15:54:31 |
Message-ID: | 0b357847c9f0d7d13f8dd5d8977b6df9@biglumber.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
> We were trying to accomplish this without having to hack the dump to
> much. We attempted adding:
>
> set local session_replication_role = replica;
>
> But that does not seem provide the expected relief.
How exactly did this fail? This should absolutely disable all
triggers for you, unless you've mucked with the triggers
and set them to replica.
- --
Greg Sabino Mullane greg(at)turnstep(dot)com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201102171053
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iEYEAREDAAYFAk1dRKIACgkQvJuQZxSWSsir0wCfQZmZkDrYBYVffyYBGYoqA/RT
VRMAoLG497FaRU7gOkpM394UT7xksXzk
=f9co
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Ahmed | 2011-02-17 15:58:46 | Re: "could not accept SSPI security context" |
Previous Message | Tom Lane | 2011-02-17 15:26:22 | Re: The efficiency of the WAL log writer |