| From: | Geoffrey Myers <lists(at)serioustechnology(dot)com> |
|---|---|
| To: | Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: disable triggers using psql |
| Date: | 2011-02-18 18:18:45 |
| Message-ID: | 4D5EB805.1040807@serioustechnology.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Greg Sabino Mullane wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
>
>> cut and paste:
>>
>> set ON_ERROR_ROLLBACK;
>
> Should be
>
> \set ON_ERROR_ROLLBACK on
>
> You can also set this when calling psql like so:
>
> psql --set ON_ERROR_ROLLBACK=on
>
> But that's getting off-topic now, as we've got the problem narrowed:
>
>> INSERT 0 1
>
> This shows the session_replication_role is working as it should. Double
> check where and how you are setting it; your foreign key problems
> will go away once it is set correctly.
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:
--
-- PostgreSQL database dump
--
SET client_encoding = 'UTF-8';
SET standard_conforming_strings = off;
SET check_function_bodies = false;
SET client_min_messages = warning;
SET escape_string_warning = off;
set session_replication_role = replica;
I'm still getting the errors. If it doesn't belong at the beginning of
this process, I'm not exactly sure where it should go.
--
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ioana Danes | 2011-02-18 18:43:10 | Logged statement apparently did not commited... |
| Previous Message | Mike Christensen | 2011-02-18 17:58:00 | Re: Any feedback on this query? |