Dump and Restore of Database by User

From: hubert(dot)palme(at)web(dot)de (Hubert Palme)
To: postgresql-bug <pgsql-bugs(at)postgresql(dot)org>
Subject: Dump and Restore of Database by User
Date: 2003-04-07 21:10:49
Message-ID: 16017.59737.700517.634390@gargle.gargle.HOWL
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

When creating a dump of a database as a user "gemein" by the command

pg_dump mitglieder >...

I get

\connect - postgres

--
-- TOC Entry ID 33 (OID 16556)
--
-- Name: "plpgsql_call_handler" () Type: FUNCTION Owner: postgres
--

CREATE FUNCTION "plpgsql_call_handler" () RETURNS opaque AS '$libdir/plpgsql', 'plpgsql_call_handler' LANGUAGE 'C';
--
-- TOC Entry ID 34 (OID 16557)
--
-- Name: plpgsql Type: PROCEDURAL LANGUAGE Owner:
--

CREATE TRUSTED PROCEDURAL LANGUAGE 'plpgsql' HANDLER "plpgsql_call_handler" LANCOMPILER '';
\connect - gemein

...

Because of the "\connect - postgres" the user cannot reload the
database himself. On the other hand, the language PL/pgSQL is available
by default in template1, so I think those lines are unnecessary:

template1=> select * from pg_language;
lanname | lanispl | lanpltrusted | lanplcallfoid | lancompiler
----------+---------+--------------+---------------+-------------
internal | f | f | 0 | n/a
C | f | f | 0 | /bin/cc
sql | f | f | 0 | postgres
plpgsql | t | t | 16556 |
(4 rows)

template1=>

So the user has to comment out those lines for the reload to work.

The same happens with the custom dump format, so this is unusable.

-- Is this a bug or a feature?

-- How can I avoid that behaviour?

I use version 7.2.1 on a Debian Linux system.

Thanks in advance,

--
Hubert Palme Am Walde 1
42119 Wuppertal
<hubert(dot)palme(at)web(dot)de>

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Ennio-Sr 2003-04-07 22:19:00 Re: Psql 'Expanded display (\x)' behaviour
Previous Message Stephan Szabo 2003-04-07 17:16:58 Re: bug with dump sql to recreate view