| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
| Cc: | teg(at)redhat(dot)com (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=), 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 16:28:12 |
| Message-ID: | 28960.996942492@sss.pgh.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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-08-04 17:11:44 | Re: Re: [BUGS] WIN32 Non Blocking |
| Previous Message | rychu | 2001-08-04 12:04:57 | Odpowied automatyczna |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-08-04 17:17:24 | Re: dumping and reloading ONLY large objects |
| Previous Message | Nils O. =?iso-8859-1?q?Sel=E5sdal?= | 2001-08-04 15:16:08 | Re: Index-speeds |