Re: HELP! BUG? pg_dump mucks up grant/revoke

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>, Trond Eivind Glomsrød <teg(at)redhat(dot)com>, 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-04 17:18:00
Message-ID: 200108041718.f74HI0V11763@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-general

> 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.
>
> I happen to agree that it'd be appropriate to put out a 7.1.3 now,
> because of the accumulated bug fixes since 7.1.2 --- not only these
> pg_dump issues, but the WAL truncation fix seems to be something that
> lots of people need. I haven't been able to stir up any interest from
> the rest of core, however.

I am interested. :-)

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2001-08-04 17:18:36 Re: Re: [BUGS] WIN32 Non Blocking
Previous Message Tom Lane 2001-08-04 17:11:44 Re: Re: [BUGS] WIN32 Non Blocking

Browse pgsql-general by date

  From Date Subject
Next Message Adam Walczykiewicz 2001-08-05 08:20:07 recurrence in PL/pgSQL ??!!!!
Previous Message Tom Lane 2001-08-04 17:17:24 Re: dumping and reloading ONLY large objects