| From: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>, "'Peter Eisentraut'" <peter_e(at)gmx(dot)net>, "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 17:28:45 |
| Message-ID: | EKEJJICOHDIEMGPNIFIJGEHCCCAA.Inoue@tpf.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
>
> 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...
>
Why do we have to have system tables per *database* ?
Is there anything wrong with global system tables ?
And how about adding dbid to pg_class,pg_proc etc ?
Regards.
Hiroshi Inoue
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-06-28 17:39:32 | Re: Big 7.1 open items |
| Previous Message | Bruce Momjian | 2000-06-28 17:27:35 | Re: Misc. consequences of backend memory management changes |