From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Thom Brown <thom(at)linux(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net> |
Subject: | Re: Problem with dumping bloom extension |
Date: | 2016-06-03 13:44:38 |
Message-ID: | CAB7nPqRgM5jQvYX0i-99T+yvG21kep-LV0qJTgp8E-Dy2JJ_Sw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jun 3, 2016 at 8:57 PM, Thom Brown <thom(at)linux(dot)com> wrote:
> If a database with the bloom extension installed is dumped and restored,
> there's an error with the access method creation:
>
> createdb bloomtest
> psql -c 'CREATE EXTENSION bloom;' bloomtest
> pg_dump -d bloomtest > ~/tmp/bloom.sql
> createdb bloomtest2
> psql -d bloomtest2 -f ~/tmp/bloom.sql
>
> The output of the last command produces:
>
> "psql:/home/thom/tmp/bloom.sql:48: ERROR: access method "bloom" already
> exists"
>
> So pg_dump shouldn't be dumping this access method as it's part of the
> extension.
Stephen, something is smelling wrong in checkExtensionMembership()
since 5d58999, an access method does not have ACLs and I would have
expected that when this routine is invoked in
selectDumpableAccessMethod() the object is not selected as dumpable.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-06-03 13:56:31 | Re: chkpass_in should not be volatile |
Previous Message | Tom Lane | 2016-06-03 13:44:30 | Re: Parallel pg_dump's error reporting doesn't work worth squat |