Bad interaction between databases
I can't seem to duplicate this but it happened once and I thought I
would mention it in case anyone else has seen it as well. I have a
table for one user and another for myself. Both tables have a table
called _key. After creating the second database (I had to destroy and
create it a few times) I looked at the first one and found that the data
in it matched the new one. I was able to drop that table and recreate
it without affecting the new one. Very strange.
--
D'Arcy J.M. Cain <darcy@{druid|vex}.net> | Democracy is three wolves
http://www.druid.net/darcy/ | and a sheep voting on
+1 416 424 2871 (DoD#0082) (eNTP) | what's for dinner.
Previously I said:
From darcy Wed Mar 4 09:52:23 1998
I can't seem to duplicate this but it happened once and I thought I
would mention it in case anyone else has seen it as well. I have a
table for one user and another for myself. Both tables have a table
called _key. After creating the second database (I had to destroy and
create it a few times) I looked at the first one and found that the data
in it matched the new one. I was able to drop that table and recreate
it without affecting the new one. Very strange.
It got more serious. After playing with the second database for a
while I managed to trash the first one altogether. I had to destroy
it and reload from a backup dump. I have never seen these problems
with PostgreSQL until I created a second database and accessed it as
a different user. I have multiple database on my other system with
no problem but I access all of them as myself, at least as far as
creating, dropping and renaming schema goes. There is some strange
interaction happening here. I'm afraid I don't know where to start
looking for this.
BTW, this is on NetBSD 1.3.
--
D'Arcy J.M. Cain <darcy@{druid|vex}.net> | Democracy is three wolves
http://www.druid.net/darcy/ | and a sheep voting on
+1 416 424 2871 (DoD#0082) (eNTP) | what's for dinner.
Import Notes
Resolved by subject fallback