On Wed, Apr 11, 2012 at 2:21 PM, Tom Lane wrote:
> ke...@omniti.com writes:
>> Using the --no-tablespaces option for pg_dumpall correctly stops tablespace
>> creation and each individual object from having its tablespace set. But if
>> the original database had its default tablespace changed, this
ke...@omniti.com writes:
> Using the --no-tablespaces option for pg_dumpall correctly stops tablespace
> creation and each individual object from having its tablespace set. But if
> the original database had its default tablespace changed, this is still
> added at the beginning of the dump file:
>
The following bug has been logged on the website:
Bug reference: 6581
Logged by: Keith Fiske
Email address: ke...@omniti.com
PostgreSQL version: 9.1.3
Operating system: Any
Description:
Using the --no-tablespaces option for pg_dumpall correctly stops tablespace
creati
