Re: disable triggers using psql - Mailing list pgsql-general

From Greg Sabino Mullane
Subject Re: disable triggers using psql
Date
Msg-id c18a70a924dd0315b523c61833c90203@biglumber.com
Whole thread Raw
In response to Re: disable triggers using psql  (Geoffrey Myers <lists@serioustechnology.com>)
Responses Re: disable triggers using psql  (Geoffrey Myers <lists@serioustechnology.com>)
List 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@turnstep.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-----



pgsql-general by date:

Previous
From: Roman
Date:
Subject: Deadlock on the same select for update
Next
From: Bill Moran
Date:
Subject: Re: Deadlock on the same select for update