u235sentinel writes:
> I have a strange problem we noticed the other day with triggers. We're
> running 8.3.3 on Solaris 10 (intel) and have a feed that comes in
> regularly to populate a table we're working on. The feed works just
> fine inserting rows however the following trigger stops the
I have a strange problem we noticed the other day with triggers. We're
running 8.3.3 on Solaris 10 (intel) and have a feed that comes in
regularly to populate a table we're working on. The feed works just
fine inserting rows however the following trigger stops the feed until
we remove the tri
Hello,
I had joined your site to post a PostgreSQL opening but had removed myself
because of getting all of these emails. Can you please remove my email address
from postgresql because I am getting endless amount of emails from technical
questions being put out there.
Thank you,
Steve
Steve M
Iñigo Martinez Lasala wrote:
> Hmm...
> No, I've not tried it. Does pg_dump perform some kind of truncating over
> bad chars? If yes, my problem would be solved!
No, I was thinking in the disabling of triggers ...
--
Alvaro Herrerahttp://www.CommandPrompt.com/
Po
Hmm...
No, I've not tried it. Does pg_dump perform some kind of truncating over
bad chars? If yes, my problem would be solved!
When actual test finish, I will try again with pg_dump from 8.2
Thank you, Alvaro.
-Original Message-
From: Alvaro Herrera
To: Iñigo Martinez Lasala
Cc: pgsql-
Iñigo Martinez Lasala wrote:
> Third one, and we haven't been able to fix it, is we cannot restore data
> dump via psql due to psql does not have an option to disable triggers.
> So, when restoring data, it fails. So... is there any way to disable in
> a psql session all triggers same way like wit
[Forgot to CC list, again]
Found the doc. page on pg_trigger I was looking for. You were right,
pg_trigger changed between 8.2 and 8.3:
http://www.postgresql.org/docs/8.2/static/catalog-pg-trigger.html
http://www.postgresql.org/docs/8.3/static/catalog-pg-trigger.html
Josh
On Wed, Feb 10, 2010 at
[Resending, forgot to CC list]
On Wed, Feb 10, 2010 at 10:47 AM, Josh Kupershmidt wrote:
>
> On Wed, Feb 10, 2010 at 10:09 AM, Iñigo Martinez Lasala <
> imarti...@vectorsf.com> wrote:
>
>> Two questions.
>>
>> I could, of course, create a data-only dump (in fact I've already done
>> it). However
H...
What about
UPDATE pg_trigger SET tgenabled = false;
Restore data, and after done:
UPDATE pg_trigger SET tgenabled = true;
I'm going to test it.
-Original Message-
From: Josh Kupershmidt
To: Iñigo Martinez Lasala
Cc: pgsql-admin
Subject: Re: [ADMIN] Disabling triggers with p
Two questions.
I could, of course, create a data-only dump (in fact I've already done
it). However, when restoring, I cannot use pg_restore since it's in
plain format, don't you? pg_restore only works with tar or compressed
formats, I think. I could restore data-only dump with psql, but then
I've
On Feb 10, 2010, at 4:30 AM, Iñigo Martinez Lasala wrote:
>
> Third one, and we haven't been able to fix it, is we cannot restore data dump
> via psql due to psql does not have an option to disable triggers. So, when
> restoring data, it fails. So... is there any way to disable in a psql sessio
Could be a valid strategy to dump in tar format, untar files, fix via
iconv each .dat file and tar them together again?
... and use pg_restore with --disable-triggers in order to avoid
constraints, of course.
-Original Message-
From: Iñigo Martinez Lasala
To: pgsql-admin
Subject: [ADMIN
Hi everybody.
We are migrating an ancient gforge postgres 7.4 database to a less
ancient postgres 8.2 one. We have not upgraded to 8.3 or 8.4 due to
problems with implicit conversion for data types (we should had to
review all sql code and we don't have time enough to do it). It's a
quite large da
13 matches
Mail list logo
