In <87r5s7q2je@newton.gmurray.org.uk> gra...@gmurray.org.uk (Graham Murray)
writes:
>Stroller writes:
>> On 9 Nov 2009, at 10:25, Konstantinos Agouros wrote:
>> I assume this is an upstream decision, and may be expected to apply to
>> 8.3.9, 8.3.10, ... also? I have no reason to "wait and
In <200911091155.35236.volkerar...@googlemail.com> volkerar...@googlemail.com
(Volker Armin Hemmann) writes:
>On Montag 09 November 2009, Konstantinos Agouros wrote:
>> Hi,
>>
>> usually upgrade within a minor version of postgres do not need a
>> pg_dump_all/ and reimport. But the upgrade from
Stroller writes:
> On 9 Nov 2009, at 10:25, Konstantinos Agouros wrote:
> I assume this is an upstream decision, and may be expected to apply to
> 8.3.9, 8.3.10, ... also? I have no reason to "wait and see if this is
> resolved", I should be careful to do a dump and restore next time I
> upgrade
On Montag 09 November 2009, Konstantinos Agouros wrote:
> Hi,
>
> usually upgrade within a minor version of postgres do not need a
> pg_dump_all/ and reimport. But the upgrade from 8.3.7 to 8.3.8 does as the
> configure option for integer-timestamps changed and thus the newly
> compiled server
On 9 Nov 2009, at 10:25, Konstantinos Agouros wrote:
...
usually upgrade within a minor version of postgres do not need a
pg_dump_all/
and reimport. But the upgrade from 8.3.7 to 8.3.8 does as the
configure option
for integer-timestamps changed and thus the newly compiled server
can not re
Hi,
usually upgrade within a minor version of postgres do not need a pg_dump_all/
and reimport. But the upgrade from 8.3.7 to 8.3.8 does as the configure option
for integer-timestamps changed and thus the newly compiled server can not read
the existing database files.
Regards,
Konstantin
--
Dip
6 matches
Mail list logo
