Re: pg_dump with postgis extension dumps rules separately

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, postgres hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump with postgis extension dumps rules separately
Date: 2013-06-01 03:46:35
Message-ID: CA+TgmoZff5KKLRR2oFwMZjbcoG0AQPHVtYu0-gi72jfEvWdAtA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 29, 2013 at 6:55 PM, Joe Conway <mail(at)joeconway(dot)com> wrote:
>> OK, simple enough. New patch attached. I still need to do some
>> testing to verify this does not break anything, but other than
>> that, any complaints (including the notion of backpatching this
>> back to 9.1)?
>
> Here's a cleaned up version, which also includes documentation. I'll
> commit back to 9.1 in a day or two unless there are any objections.

Changing SQL syntax in the back-branches isn't normally something we
do, but I confess I don't see any real reason not to do it in this
case.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2013-06-01 06:08:14 Re: [PATCH] add --progress option to pgbench (submission 3)
Previous Message Robert Haas 2013-06-01 03:42:51 Re: extensible external toast tuple support