Re: BUG #8695: Reloading dump fails at COMMENT ON EXTENSION plpgsql

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: chris(at)chrullrich(dot)net, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #8695: Reloading dump fails at COMMENT ON EXTENSION plpgsql
Date: 2014-04-10 03:13:57
Message-ID: 1420.1397099637@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> That's what I thought too, but I see a schema file in pg_extensions:

Read the manual.

> Should we hard-code a pg_catalog plpgsql to be skipped in pg_dump?

No, I don't think so.

The real issue here is that we don't have a notion of a "built-in
extension". I think this was specifically debated back when we
extension-ified plpgsql, though I don't recall details of why
we ended up not doing that. Maybe the idea was that you could
drop and then re-add plpgsql? Anyway, I think this is not such
a simple issue and a one-line hack in pg_dump is not likely to
improve matters.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Geoghegan 2014-04-10 05:47:49 log_checkpoints, microseconds
Previous Message Bruce Momjian 2014-04-10 02:43:45 Re: BUG #8695: Reloading dump fails at COMMENT ON EXTENSION plpgsql