From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_dump with postgis extension dumps rules separately |
Date: | 2013-05-29 14:35:42 |
Message-ID: | 51A6123E.3080205@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/29/2013 05:52 AM, Dimitri Fontaine wrote:
> Andres Freund <andres(at)2ndquadrant(dot)com> writes:
>> On 2013-05-29 09:30:43 +0200, Dimitri Fontaine wrote:
>>>> 2) How should we handle already installed extensions, which
>>>> will still lack dependency records after this bugfix?
>>>
>>> I don't really see any other way here than providing an upgrade
>>> script that will somehow re-attach those objects, either by
>>> directly messing with pg_depends (that is, when there's a
>>> systematic way to get the OIDs of the missing RULEs), or by
>>> maybe doing a drop/create on the RULEs?
>>
>> Couldn't ALTER EXTENSION ... ADD ...; be brought up to speed to
>> support this?
>
> I'll blame the Time Zone Difference Recovering. I felt like
> missing something…
Seems like the perfect idea, but is that something we would backpatch?
Joe
- --
Joe Conway
credativ LLC: http://www.credativ.us
Linux, PostgreSQL, and general Open Source
Training, Service, Consulting, & 24x7 Support
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJRphI+AAoJEDfy90M199hl4HgP/3LdS4YsE8IiwadEKxDZeBEP
ubtS4a2CwNrWwATpScK7H8BHQfB2Jd7uw5+HeXTbbSdmt2XFz/fCcQtaTuJRNwUw
8OHlqqS9mrgsKHgzE9+1wCUBfmpsldBaw7HetmNnacrQICVir0YXTbHfBewH/wAT
BQ+9qjLXom8gLgZ1rSysa/V4QEYdCMCSIsW/A55zkpAcvIfACmGxgzL9msoMiWxR
qdWIMd9Pop8yrAO/r3e64TG+48V18/U17mdhhPx3/svH9FP+Nee4N6t1AozNETUN
OHVJDCZmxa0k3mCj4lJud95qARDLa+1PZ+FMf5tk9+WVlUdT9tMh66RBKilmyaBk
WZReY3plRaK74xnDPo/M5a0PVu7SDaqQVWXArzorZLf5J3hL0LUE8EmkGXYZk860
WpUFOMVZqux96NmFhgNgOuNBCHQN3zztCGwgHA6Y26ajIQQnYs74XnNo/kGdje1h
A16dmxLWUEwthpPoU/DyRrObavIWI6OMMUDZ3TlQ0CK8KziLGgD2JV4uzXjyrm+w
xwNFbR5j6dFkolO32Z8v01JHH1iKCQhMo9TzTAP8w9oRPvYVxX7QbotCKV7+X0mu
uBmAB9y3EjiVvuHCkuDFw2tJ/u9/p9R0cbJYdEzNyOvG22/LL6/RaTgyjg6d+jZN
Mso43jWnjh2O6Cxy0v6N
=Mf13
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2013-05-29 14:36:07 | Re: fallocate / posix_fallocate for new WAL file creation (etc...) |
Previous Message | Peter Eisentraut | 2013-05-29 14:12:54 | Re: fallocate / posix_fallocate for new WAL file creation (etc...) |