| From: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com> | 
|---|---|
| To: | pgsql-general(at)postgresql(dot)org | 
| Cc: | lists(at)serioustechnology(dot)com | 
| Subject: | Re: disable triggers using psql | 
| Date: | 2011-02-21 20:32:34 | 
| Message-ID: | c18a70a924dd0315b523c61833c90203@biglumber.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
> The saga continues.  I've reverted to a multi-step process to try and 
> figure this out.  I create the initial database, then load it from the 
> command line psql as follows:
> 
> pro-# \set session_replication_role replica;
> pro-# \o db.out
> pro-# \i dump.txt
This is a database set, not a psql on, so you do not want the 
backslash before the "set". 
SET session_replication_role = replica;
I'd recommend adding a:
SHOW session_replication_role;
to the dump.txt as a sanity check.
- -- 
Greg Sabino Mullane greg(at)turnstep(dot)com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201102211529
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iEYEAREDAAYFAk1iy74ACgkQvJuQZxSWSsgWQACgrxKDvN/yCZD5GZJvlqFMyyIC
9mwAnjOMJ9QDRa3IoiBCvaS9mT5sMR6f
=JYCs
-----END PGP SIGNATURE-----
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bill Moran | 2011-02-21 20:50:11 | Re: Deadlock on the same select for update | 
| Previous Message | Joel Reed | 2011-02-21 20:06:58 | string_agg hanging? |