Re: mistakes in postgresql-snapshots (7.3) - Mailing list pgsql-bugs

From Peter Eisentraut
Subject Re: mistakes in postgresql-snapshots (7.3)
Date
Msg-id Pine.LNX.4.44.0208141944420.20055-100000@localhost.localdomain
Whole thread Raw
In response to Re: mistakes in postgresql-snapshots (7.3)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: mistakes in postgresql-snapshots (7.3)  (Bruce Momjian <pgman@candle.pha.pa.us>)
List 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@gmx.net

pgsql-bugs by date:

Previous
From: "Sasa Markovic"
Date:
Subject: Long strings, short varchars
Next
From: Bruce Momjian
Date:
Subject: Re: Bug #737: PQescapeBytea parameter #3 size_t *to_length