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

From Geoffrey Myers
Subject Re: disable triggers using psql
Date
Msg-id 4D63B38D.90302@serioustechnology.com
Whole thread Raw
In response to Re: disable triggers using psql  ("Greg Sabino Mullane" <greg@turnstep.com>)
List pgsql-general
Greg Sabino Mullane wrote:
> -----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.

For the sake of completeness, I've attempted the above, same result.  We
have decided to take a different approach and attempt to clean up the
data in the database, then convert.

I do appreciate all the time you've devoted to this.  There must be
something in the dump that is causing these issues.

Thanks again Greg.  I'll certainly update the list once we have a
working solution.

>
> - --
> 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-----
>
>
>


--
Until later, Geoffrey

"I predict future happiness for America if they can prevent
the government from wasting the labors of the people under
the pretense of taking care of them."
- Thomas Jefferson

pgsql-general by date:

Previous
From: Jens Wilke
Date:
Subject: Re: Mysql to Postgresql
Next
From: Melvin Davidson
Date:
Subject: Re: why is there no TRIGGER ON SELECT ?