From: | teg(at)redhat(dot)com (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=) |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>, Keith F Irwin <kirwin14(at)home(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: HELP! BUG? pg_dump mucks up grant/revoke |
Date: | 2001-08-05 15:45:08 |
Message-ID: | xuyelqqjyt7.fsf@halden.devel.redhat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-general |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> writes:
> > A pg_dump that can't be restored should be a release forcer, IMHO.
>
> Let's not panic here. The actual net effect of these bugs will be that
> the pg_dump output script fails to restore the permissions and/or
> comment associated with a view. Which'd be annoying, but hardly
> something to ruin your whole day.
The impact will vary from location to location... but given that this
is the only way to upgrade the database (as you know, this is one of
my pet peeves), it needs to work.
> pg_dump issues, but the WAL truncation fix seems to be something that
> lots of people need.
Are those also in the 7.1-stable branch?
--
Trond Eivind Glomsrød
Red Hat, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-08-05 16:04:46 | Re: HELP! BUG? pg_dump mucks up grant/revoke |
Previous Message | Karl DeBisschop | 2001-08-05 13:54:01 | Re: HELP! BUG? pg_dump mucks up grant/revoke |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-08-05 16:04:46 | Re: HELP! BUG? pg_dump mucks up grant/revoke |
Previous Message | Karl DeBisschop | 2001-08-05 13:54:01 | Re: HELP! BUG? pg_dump mucks up grant/revoke |