Re: [HACKERS] pgsql-server: Tablespaces.
Hm ... seems like that requires more special cases, not fewer. What I was imagining was the current database-local pg_description plus a single shared table pg_shared_description. When you add more kinds of shared objects (SQL roles maybe?) obj_description doesn't need to change... Oh yeah, that's a much better idea :) Didn't think of that :) Chris ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] pgsql-server: Tablespaces.
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes: >> Perhaps we should think about creating a shared version of >> pg_description so we could have more reasonable support for comments >> on shared objects. I'm not in a hurry for this but it would be a >> reasonable TODO item. > Just add a comment text column to the databases, users, groups and > tablespaces tables. Then special case them in obj_description. Hm ... seems like that requires more special cases, not fewer. What I was imagining was the current database-local pg_description plus a single shared table pg_shared_description. When you add more kinds of shared objects (SQL roles maybe?) obj_description doesn't need to change... regards, tom lane ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] pgsql-server: Tablespaces.
Well, it has the same issues as COMMENT ON DATABASE, which we support, though crudely. Perhaps we should think about creating a shared version of pg_description so we could have more reasonable support for comments on shared objects. I'm not in a hurry for this but it would be a reasonable TODO item. Just add a comment text column to the databases, users, groups and tablespaces tables. Then special case them in obj_description. Chris ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [HACKERS] pgsql-server: Tablespaces.
Tom Lane wrote: Christopher Kings-Lynne <[EMAIL PROTECTED]> writes: Comment on TABLESPACE is impossible, no? Tablespaces are a global relation and pg_description isn't. Well, it has the same issues as COMMENT ON DATABASE, which we support, though crudely. Perhaps we should think about creating a shared version of pg_description so we could have more reasonable support for comments on shared objects. I'm not in a hurry for this but it would be a reasonable TODO item. There are more sharing issues with tablespaces (which are already supported in pgadmin3, btw :-) To drop a tablespace, it must be empty, but it can be quite painful to find out which objects are populating it. Currently, every database has to be queried for pg_class.reltablespace=. I'd love to show tablespace dependency information, which would require some sort of global pg_namespace, pg_class and pg_index. Any thoughts about this? Regards, Andreas ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] pgsql-server: Tablespaces.
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes: > Comment on TABLESPACE is impossible, no? Tablespaces are a global > relation and pg_description isn't. Well, it has the same issues as COMMENT ON DATABASE, which we support, though crudely. Perhaps we should think about creating a shared version of pg_description so we could have more reasonable support for comments on shared objects. I'm not in a hurry for this but it would be a reasonable TODO item. regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [HACKERS] pgsql-server: Tablespaces.
(Moved to -hackers) Log Message: --- Tablespaces. Alternate database locations are dead, long live tablespaces. Sweet :) There are various things left to do: contrib dbsize and oid2name modules need work, and so does the documentation. Also someone should think about COMMENT ON TABLESPACE and maybe RENAME TABLESPACE. Also initlocation is dead, it just doesn't know it yet. Comment on TABLESPACE is impossible, no? Tablespaces are a global relation and pg_description isn't. I'll do RENAME and OWNER TO for tablespaces with this patch I'm working on atm if people like. Chris ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
