Gavin Sherry <swm@linuxworld.com.au> writes:
> [ ... in Oracle: ]
> So, when you create a new database, you can determine where the 'system
> catalogs' are by setting the datafile location for the system catalog
> tablespaces. You can *also* set a default tablespace for the database --
> default in the sense that all newly created objects with no explicit
> tablespace clause are created in the tablespace. With an exception as
> follows: Oracle relies heavily on the concept of a user's default
> tablespace. Interestingly, this is what you just mentioned above :-).
So if we went with a GUC-driven approach, we could emulate both of those
things easily, because people could set the default_tablespace GUC
variable in either ALTER DATABASE or ALTER USER. This is starting to
sound like a win.
regards, tom lane
