From: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
---|---|
To: | lists(at)serioustechnology(dot)com |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: disable triggers using psql |
Date: | 2011-02-18 19:09:28 |
Message-ID: | 28fd6ffbd42d0f6091294c33282a3868@biglumber.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
> I'm not sure how to address this. I'm not exactly sure where to place
> session_replication_role. It's very close to the top of the file:
Is this a pg_dumpall? A \connect later on will reset the
session_replication_role. If so, add the SET right after
the \connect. Alternatively, you could create a special user
to invoke psql as, which has:
ALTER USER dangerous_bob SET session_replication_role = replica;
Be *very* careful with that account though, as using it for
anything other than this special case could be very bad.
- --
Greg Sabino Mullane greg(at)turnstep(dot)com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201102181408
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iEYEAREDAAYFAk1ew9MACgkQvJuQZxSWSshETwCg2oEEicHhokORuQRl3sxkLkpj
ghIAnRe02LCuyyRlyzvKZ67QCYUyfPzC
=H9Wb
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Norberto Delle | 2011-02-18 19:27:41 | Canceling a DELETE query |
Previous Message | Ioana Danes | 2011-02-18 18:43:10 | Logged statement apparently did not commited... |