Peter Eisentraut writes:
> On fre, 2012-05-18 at 19:57 +, erlko...@talisman.org wrote:
>> Given compatibility concerns, renaming
>> it is probably infeasible. However, being able to parameterize the
>> length, defaulting to 6 bytes, would be adequate.
> That could be a workable solution.
Th
l...@pcorp.us writes:
> This seems to be only an issue if a user individually chooses to backup a
> table marked as editable in an extension, but works fine if full backup is
> chosen.
AFAICT this is a misunderstanding of the intended behavior of extension
configuration tables. The data in them w
Tom,
Okay understood. We had planned to do something along this line of having a
where condition for the extension or putting the custom spatial_ref_sys in a
separate table but hand't decided which way to go. So that will take care of
the handling custom records issue.
So I guess the more major
Excerpts from grv87's message of sáb may 19 10:28:47 -0400 2012:
> The following bug has been logged on the website:
>
> Bug reference: 6652
> Logged by: Basil Peace
> Email address: gr...@yandex.ru
> PostgreSQL version: 9.1.3
> Operating system: Windows 7 x64
> Description:
On 18 May 2012 23:06, Edmund Horner wrote:
> I ran into a bit of trouble running pg_upgrade to upgrade from my
> 9.1.3 cluster. This is the first time I have run pg_upgrade. It is
> entirely possible I've done something wrong.
>
> As a control, I was able to successfully "upgrade" the Postgresq
