Обсуждение: Two tables with same name in different user not allowed ?
Hi , I have two users in my database x & y. I tried to create a table abc in y which is there in x with the same name.Ofcourse i logged in as user y and tried. Even then am not allowed to create throwing error that "object already exist". Can anybody xplain this comparing Oracle-schema with the user in postgres as am in the process of porting oracle schemas to postgres`. thanks laks
Вложения
Kumar, Lakshmi (Cognizant) wrote: > Hi , > I have two users in my database x & y. > I tried to create a table abc in y which is there in x with the same > name.Ofcourse i logged in as user y and tried. > Even then am not allowed to create throwing error that "object already > exist". > Can anybody xplain this comparing Oracle-schema with the user in postgres > as am in the process of porting oracle schemas to postgres`. We don't have schemas but hope to have them in 7.3. Right now, you can create temp tables with duplicate names but they go away on session exit. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
We are currently using Postgresql 7.1.2, running on a E3500 server, OS
Solaris 2.6. We would like to upgrade to postgresql 7.2.
1) Do you all consider it stable enough now to upgrade?
2) If I understand correctly, to upgrade, step would be:
a) pg_dumpall
b) reset PGHOME to new version of postgresql
c) pg_restore
Is this correct?
If so, that seems pretty drastic. I cannot imagine that once our databases
start getting really huge that this will last as an upgrade method. I
thought we would be using pg_upgrade, but I see a note that it will not
work with versions of postgres 7.1 and higher.
Why did pg_upgrade go away, and can we look forward to one in the future?
Thanks,
Naomi
--
Naomi Walker
Chief Information Officer
Eldorado Computing, Inc.
602-604-3100 ext 242
Naomi Walker wrote: > We are currently using Postgresql 7.1.2, running on a E3500 server, OS > Solaris 2.6. We would like to upgrade to postgresql 7.2. > > 1) Do you all consider it stable enough now to upgrade? > > 2) If I understand correctly, to upgrade, step would be: > > a) pg_dumpall > b) reset PGHOME to new version of postgresql > c) pg_restore > > Is this correct? > > If so, that seems pretty drastic. I cannot imagine that once our databases > start getting really huge that this will last as an upgrade method. I > thought we would be using pg_upgrade, but I see a note that it will not > work with versions of postgres 7.1 and higher. > > Why did pg_upgrade go away, and can we look forward to one in the future? It is in /contrib/pg_upgrade now and it does work for 7.1 upgrades, though it is only lightly tested. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
At 01:53 PM 2/8/02 -0500, Bruce Momjian wrote: >Naomi Walker wrote: > > We are currently using Postgresql 7.1.2, running on a E3500 server, OS > > Solaris 2.6. We would like to upgrade to postgresql 7.2. > > > > 1) Do you all consider it stable enough now to upgrade? > > > > 2) If I understand correctly, to upgrade, step would be: > > > > a) pg_dumpall > > b) reset PGHOME to new version of postgresql > > c) pg_restore > > > > Is this correct? > > > > If so, that seems pretty drastic. I cannot imagine that once our > databases > > start getting really huge that this will last as an upgrade method. I > > thought we would be using pg_upgrade, but I see a note that it will not > > work with versions of postgres 7.1 and higher. > > > > Why did pg_upgrade go away, and can we look forward to one in the future? > >It is in /contrib/pg_upgrade now and it does work for 7.1 upgrades, >though it is only lightly tested. Bruce, are you saying I can use /contrib/pg_upgrade for my 7.1.2 to 7.2 upgrade? -- Naomi Walker Chief Information Officer Eldorado Computing, Inc. 602-604-3100 ext 242
Chad, hold up a bit. Bruce and I are talking, and i'm asking the same things. At 02:27 PM 2/8/02 -0700, Chad R. Larson wrote: >At 11:53 AM 2/8/2002 , Bruce Momjian wrote: >>It is in /contrib/pg_upgrade now and it does work for 7.1 upgrades, >>though it is only lightly tested. > >When you say "work for 7.1 upgrades" I assume you mean like from 7.1.2 to >7.1.3. Is there a 7.1.2 to 7.2 version? Would one be hard to write, >given the existing one as a model? > > > -crl >-- >Chad R. Larson (CRL22) chad@eldocomp.com > Eldorado Computing, Inc. 602-604-3100 > 5353 North 16th Street, Suite 400 > Phoenix, Arizona 85016-3228 -- Naomi Walker Chief Information Officer Eldorado Computing, Inc. 602-604-3100 ext 242