| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Another nasty pg_dump problem |
| Date: | 2003-08-01 13:31:26 |
| Message-ID: | 7435.1059744686@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> This could be fixed, but note that elsewhere we use
> /*
> * Always start with REVOKE ALL FROM PUBLIC, so that we don't have to
> * wire-in knowledge about the default public privileges for different
> * kinds of objects.
> */
> appendPQExpBuffer(firstsql, "REVOKE ALL ON %s %s FROM PUBLIC;\n",
> type, name);
> So maybe this isn't such a bad state after all.
Well, if you want to take that position then the test for "{=UC}" ought
to be ripped out, so that we are consistent about it across backend
versions.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-08-01 13:45:32 | Re: SQLSTATEs for warnings |
| Previous Message | Peter Eisentraut | 2003-08-01 12:27:31 | Re: SQLSTATEs for warnings |