| From: | Laurette Cisneros <laurette(at)nextbus(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: foreign key problem |
| Date: | 2002-10-09 23:16:23 |
| Message-ID: | Pine.LNX.4.44.0210091613590.2174-100000@visor.corp.nextbus.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
7.2.3.
It's a mystery as to how this happened but there is a program we use to
copy rows from one version to another. For some reason the person who
wrote it disabled triggers before copying rows to a new version then
re-enabled the triggers. If someone made changes while the triggers were
off then this could happen. At least that's my story and I'm sticking to
it.
So, the program has been fixed and we hope this plugs the hole that that
rabbit went down.
Thanks,
L.
On Sun, 6 Oct 2002, Josh Berkus wrote:
> Laurette,
>
> > How is this possible? I've tried to reproduce this, but haven't been able
> > to yet. This has happened to use several times.
>
> Oh, forgot question 2:
> SELECT version()?
>
>
--
Laurette Cisneros
The Database Group
(510) 420-3137
NextBus Information Systems, Inc.
www.nextbus.com
------------------------------
It's 10 o'clock...
Do you know where your bus is?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ludwig Lim | 2002-10-10 07:27:26 | Viewing stored procedure code |
| Previous Message | Manfred Koizar | 2002-10-09 18:09:03 | Re: [pgsql-performance] Large databases, performance |