Christopher Kings-Lynne wrote: > > It is a little bit different because a schema, a table or a function are > > database application issues and are normally addressed by pg_dump and > > pg_restore, although tablespaces are more an administration issue wrt disk > > layout and the like, which are likely to be different from one machine to > > another (compare with I obviously want the same schema/table/function for > > my application). So the notion of dump/restore of a tablespace need > > some careful thinking. > > > > But maybe I'm just stupid to dream that I could restore or transfer my > > data even if I used a tablespace somewhere? ;-) > > OK, perhaps. It it not easy to implement however, since the tablespace > clause on indexes comes from the pg_get_indexdef() function and isn't > added by pg_dump. > > Bruce - pg_dump TODO for --no-tablespace or something?
Uh, TODO already has: * Allow database recovery where tablespaces can't be created When a pg_dump is restored, all tablespaces will attempt to be created in their original locations. If this fails, the user must be able to adjust the restore process. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
