| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, 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 15:07:53 |
| Message-ID: | 21134.1370099273@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Joe Conway <mail(at)joeconway(dot)com> writes:
> On 05/31/2013 08:46 PM, Robert Haas wrote:
>> 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.
> That was part of my hesitation, but I don't see any better way to fix
> existing installations and this is pretty well self-contained. Any
> other opinions out there?
I don't like this approach much.
1. It does nothing to fix the issue in *existing* databases, which
won't have pg_depend entries like this.
2. In general, we have assumed that properties of tables, such as
indexes and constraints, cannot be independent members of extensions.
It's not clear to me why rules should be different.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2013-06-01 15:11:26 | Re: detecting binary backup in progress |
| Previous Message | Joe Conway | 2013-06-01 14:57:32 | Re: pg_dump with postgis extension dumps rules separately |