Re: pg_dump cosmetic problem while dumping/restoring rules

From: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Gražvydas Valeika <gvaleika(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump cosmetic problem while dumping/restoring rules
Date: 2012-12-11 22:43:10
Message-ID: m2fw3cdxc1.fsf@2ndQuadrant.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)2ndquadrant(dot)com> writes:
>> pg_restore: [archiver (db)] Error from TOC entry 3874; 2618 396850 RULE
>> geometry_columns_delete postgres
>> pg_restore: [archiver (db)] could not execute query: ERROR: rule
>> "geometry_columns_delete" for relation "geometry_columns" already exists
>> Command was: CREATE RULE geometry_columns_delete AS ON DELETE TO
>> geometry_columns DO INSTEAD NOTHING;
>>
>> This happens because in the beginning of backup file there is issued
>> command
>> CREATE EXTENSION IF NOT EXISTS postgis WITH SCHEMA public;
>> which creates those rules.
>
>> As I understand these errors are harmless, I would say - cosmetic defects.
>
> I'd say this is actually a real bug in the extensions tracking of
> dependencies.
> And it would have caused a failed restore if you had used single
> transaction mode.

Indeed. I will look into that.

Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dimitri Fontaine 2012-12-11 22:51:25 Re: Re: [PATCH 02/14] Add support for a generic wal reading facility dubbed XLogReader
Previous Message Tom Lane 2012-12-11 22:24:08 Re: Re: [PATCH 02/14] Add support for a generic wal reading facility dubbed XLogReader