| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz>, <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: mistakes in postgresql-snapshots (7.3) |
| Date: | 2002-08-14 18:49:20 |
| Message-ID: | Pine.LNX.4.44.0208141944420.20055-100000@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Tom Lane writes:
> pg_dumpall doesn't yet do the right thing at the database level, but I
> believe he's planning to take care of that.
I have never heard of database privileges, except that people occasionally
expect me to fix something about them. :-/
> I'm not sure there is anything we can do about this without making
> life worse. But it's annoying. Any thoughts?
There are a couple of simple recipes we can give to users, such as
UPDATE pg_language SET lanacl = '{"=U"}' WHERE lanpltrusted;
UPDATE pg_proc SET proacl = '{"=X"}' WHERE proacl IS NULL;
The trick is that you'd need to run the first line before creating any
functions. Blech.
--
Peter Eisentraut peter_e(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-08-15 03:01:18 | Re: Bug #737: PQescapeBytea parameter #3 size_t *to_length |
| Previous Message | Sasa Markovic | 2002-08-14 18:41:29 | Long strings, short varchars |