Re: REVIEW: Extensions support for pg_dump

From: Kääriäinen Anssi <anssi(dot)kaariainen(at)thl(dot)fi>
To: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: REVIEW: Extensions support for pg_dump
Date: 2011-01-17 17:58:48
Message-ID: BC19EF15D84DC143A22D6A8F2590F0A76515EE97CD@EXMAIL.stakes.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Well I'm not seeing that here

I am not at work at the moment and I don't have the possibility to compile PostgreSQL on this computer, so the example here is from memory.

The issue I saw was this: assume you have an extension foo, containing one function, test().

CREATE EXTENSION foo;
DROP FUNCTION test();
-- restricted due to dependency

ALTER FUNCTION test() RENAME TO test2;
DROP FUNCTION test2();
-- not restricted!

The same can be done using CREATE OR REPLACE.

I hope this is not an error on my part. It is possible because I had a lot of schemas and my search_path might have been wrong...

- Anssi
PS: Using web email client, I hope this comes out in somewhat sane format.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2011-01-17 18:07:42 Re: What happened to open_sync_without_odirect?
Previous Message Robert Haas 2011-01-17 17:56:05 Re: Moving test_fsync to /contrib?