| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>, "'Peter Eisentraut'" <peter_e(at)gmx(dot)net>, "'Hiroshi Inoue'" <Inoue(at)tpf(dot)co(dot)jp>, Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>, Jan Wieck <JanWieck(at)Yahoo(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu> |
| Subject: | Re: Big 7.1 open items |
| Date: | 2000-06-28 16:40:53 |
| Message-ID: | 200006281640.MAA13366@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> However I do see a bit of a problem here: since DROP DATABASE is
> ordinarily executed by a backend that's running in a different database,
> how's it going to read pg_class of the target database? Perhaps it will
> be necessary to fire up a sub-backend that runs in the target DB for
> long enough to kill all the user tables. Looking messy...
That was my feeling. Imagine another issue. If you see a file, how do
you figure out what database it belong to? You would have to cycle
through the pg_class relations for every database. Seems such reverse
lookups would not be impossible. Not sure if it will ever be required.
--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karel Zak | 2000-06-28 16:46:30 | Re: ./configure bug in CVS |
| Previous Message | Daniel Freedman | 2000-06-28 16:39:45 | MySQL has gone GPL |