pg_dump COMMENT ON DATABASE sometimes inappropriate - Mailing list pgsql-hackers

From Michael Fuhr
Subject pg_dump COMMENT ON DATABASE sometimes inappropriate
Date
Msg-id 20050921051011.GA40287@winnie.fuhr.org
Whole thread Raw
Responses Re: pg_dump COMMENT ON DATABASE sometimes inappropriate
Re: pg_dump COMMENT ON DATABASE sometimes inappropriate
List pgsql-hackers
pg_dump emits COMMENT ON DATABASE (if the database has a comment)
even when dumping only an individual schema or table.  That seems
inappropriate, especially when copying data to a different cluster
where the named database might not exist or might have a different
comment that shouldn't be overwritten.  Does anybody else think
pg_dump shouldn't emit COMMENT ON DATABASE in these cases?

-- 
Michael Fuhr


pgsql-hackers by date:

Previous
From: Oleg Bartunov
Date:
Subject: Re: passing parameters to CREATE INDEX
Next
From: Hannu Krosing
Date:
Subject: Re: passing parameters to CREATE INDEX