On Sun, Oct 6, 2013 at 11:20:14PM +0800, Patrick Dung wrote:
> Noted and thanks.
>
> I can see that it should be updated in the devel manual page:
> http://www.postgresql.org/docs/devel/static/pgupgrade.html
Yes, it is updated now, it just takes a few hours.
--
Bruce Momjian http://
t;
; Ivan Voras ; Tom Lane
Sent: Saturday, October 5, 2013 10:19 PM
Subject: Re: [GENERAL] Major upgrade of PostgreSQL and MySQL
On Sat, Sep 14, 2013 at 01:54:40AM +0800, Patrick Dung wrote:
> 1. In the past, I have an impression that it requires double of the database
> size.
> Because
; Cc: Ivan Voras; Tom Lane
> Subject: Re: [GENERAL] Major upgrade of PostgreSQL and MySQL
>
> 3. But the way, if users is using Windows, is the link option still works?
>
> Thanks,
> Patrick
>
>
> It definitely works.
Yes, uses Windows junction points. I have
On Sat, Sep 14, 2013 at 01:54:40AM +0800, Patrick Dung wrote:
> 1. In the past, I have an impression that it requires double of the database
> size.
> Because the manual present in a way that it 'must' need to hold the old and
> new
> database cluster.
> But it does not mention the benefit of usin
>
>Symbolic links being used.
>It also creates batch file that could be used to delete old cluster after
>upgrade.
>It's all in the docs.
>
>Regards,
>Igor Neyman
I see, it should be this step:
Delete old cluster
Once you are satisfied with the upgrade, you can delete the old cluster's data
d
: [GENERAL] Major upgrade of PostgreSQL and MySQL
On 13 September 2013 21:44, Patrick Dung wrote:
> Ivan Voras has replied that the link method work fine in Windows on another
> thread.
That would be very surprising since I don't run Windows servers :)
On 13 September 2013 21:44, Patrick Dung wrote:
> Ivan Voras has replied that the link method work fine in Windows on another
> thread.
That would be very surprising since I don't run Windows servers :)
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to y
From: Patrick Dung [mailto:patrick_...@yahoo.com.hk]
Sent: Friday, September 13, 2013 3:50 PM
To: Igor Neyman; Stephen Frost
Cc: pgsql-general@postgresql.org; Ivan Voras; Tom Lane
Subject: Re: [GENERAL] Major upgrade of PostgreSQL and MySQL
For Windows, is it using symbolic links or hard
From: Igor Neyman
To: Stephen Frost ; Patrick Dung
Cc: "pgsql-general@postgresql.org" ; Ivan Voras
; Tom Lane
Sent: Saturday, September 14, 2013 2:14 AM
Subject: RE: [GENERAL] Major upgrade of PostgreSQL and MySQL
Hi Igor,
>> -
From: Stephen Frost
To: Patrick Dung
Cc: "pgsql-general@postgresql.org" ; Ivan Voras
; Tom Lane
Sent: Saturday, September 14, 2013 2:05 AM
Subject: Re: [GENERAL] Major upgrade of PostgreSQL and MySQL
Hi Stephen,
>Patrick,
>
>* Pat
Patrick,
* Patrick Dung (patrick_...@yahoo.com.hk) wrote:
> I think the documentation could put a note at the beginning for new users.
Yes, probably true. Feel free to propose specific improvements.
> 2. Also I think the documentation should provide more info for users that use
> packages.
> M
: Re: [GENERAL] Major upgrade of PostgreSQL and MySQL
>
>
> > 3. But the way, if users is using Windows, is the link option still works?
>
> Don't think so, but not sure. pg_upgrade could be made to work in a truely
> "in-place" method if there's demand f
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Patrick Dung
Sent: Friday, September 13, 2013 1:55 PM
To: Stephen Frost; pgsql-general@postgresql.org
Cc: Ivan Voras; Tom Lane
Subject: Re: [GENERAL] Major upgrade of PostgreSQL and MySQL
3. But
On Fri, Sep 13, 2013 at 11:13 AM, Stephen Frost wrote:
> Patrick,
>
>
> On Friday, September 13, 2013, Patrick Dung wrote:
>>
>> >What? That's absolutely *not* required for pg_upgrade to work. In
>> >general, I would recommend that you make a copy of the database, but
>> >it's certainly not requ
From: Stephen Frost
To: Patrick Dung
Cc: "pgsql-general@postgresql.org" ; Ivan Voras
; Tom Lane ; Stephen Frost
Sent: Saturday, September 14, 2013 1:13 AM
Subject: Re: [GENERAL] Major upgrade of PostgreSQL and MySQL
On Friday, September 13, 2013, Patrick Dung wrote:
>
From: Thomas Kellerer
To: pgsql-general@postgresql.org
Sent: Saturday, September 14, 2013 12:27 AM
Subject: Re: [GENERAL] Major upgrade of PostgreSQL and MySQL
Patrick Dung wrote on 13.09.2013 18:17:
>> The problem of pg_upgrade is that it needed t
From: Stephen Frost
To: Patrick Dung
Cc: "pgsql-general@postgresql.org" ; Ivan Voras
; Tom Lane
Sent: Saturday, September 14, 2013 12:43 AM
Subject: Re: [GENERAL] Major upgrade of PostgreSQL and MySQL
* Patrick Dung (patrick_...@yahoo.com
Patrick,
On Friday, September 13, 2013, Patrick Dung wrote:
>
> >What? That's absolutely *not* required for pg_upgrade to work. In
> >general, I would recommend that you make a copy of the database, but
> >it's certainly not required.
>
> I mean the old version and new version would need to take
* Patrick Dung (patrick_...@yahoo.com.hk) wrote:
> The problem of pg_upgrade is that it needed to hold two set of databases data
> in the server.
What? That's absolutely *not* required for pg_upgrade to work. In
general, I would recommend that you make a copy of the database, but
it's certainly
On Fri, Sep 13, 2013 at 11:17 AM, Patrick Dung wrote:
>
>
> From: Tom Lane
> To: Stephen Frost
> Cc: Ivan Voras ; pgsql-general@postgresql.org
> Sent: Friday, September 13, 2013 9:58 PM
>
> Subject: Re: [GENERAL] Major upgrade
From: Tom Lane
To: Stephen Frost
Cc: Ivan Voras ; pgsql-general@postgresql.org
Sent: Friday, September 13, 2013 9:58 PM
Subject: Re: [GENERAL] Major upgrade of PostgreSQL and MySQL
>> * Ivan Voras (ivo...@freebsd.org) wrote:
>>>
Patrick Dung wrote on 13.09.2013 18:17:
The problem of pg_upgrade is that it needed to hold two set of databases data
in the server.
This is not be desirable (very slow) or possible (space limitation) for
database with huge data.
For example, if the old version is already using over 50% of the
Stephen Frost writes:
> * Ivan Voras (ivo...@freebsd.org) wrote:
>> If I read the documentation correctly
>> (http://www.postgresql.org/docs/9.3/static/pgupgrade.html), it needs
>> oldbindir and newbindir arguments pointing to the directories of
>> PostgreSQL executables for the old and new versio
* Ivan Voras (ivo...@freebsd.org) wrote:
> If I read the documentation correctly
> (http://www.postgresql.org/docs/9.3/static/pgupgrade.html), it needs
> oldbindir and newbindir arguments pointing to the directories of
> PostgreSQL executables for the old and new versions, making it basically
> unu
On 12/09/2013 18:16, Karl Denninger wrote:
>
> On 9/12/2013 11:11 AM, Patrick Dung wrote:
>> While reading some manual of PostgreSQL and MySQL (eg.
>> http://dev.mysql.com/doc/refman/5.1/en/upgrading-from-previous-series.html).
>>
>> I have found that MySQL has stated many incompatibilities and kn
While reading some manual of PostgreSQL and MySQL (eg.
http://dev.mysql.com/doc/refman/5.1/en/upgrading-from-previous-series.html).
I have found that MySQL has stated many incompatibilities and know issues (a
long list) in the MySQL version 5.0, 5.1, 5.5, 5.6 and 5.7.
For PostgreSQL, it seems I
Patrick Dung wrote on 12.09.2013 18:11:
For PostgreSQL, it seems I can't find the list (it just say see the
Appendix E / release notes). I think it is a plus for PostgreSQL if
it has few incompatibilities between major versions.
There is such a list in the release notes:
http://www.postgresql.
Merlin Moncure wrote on 12.09.2013 18:37:
By the way, for in-place major version upgrade (not dumping DB and
import again), MySQL is doing a better job in here.
http://www.postgresql.org/docs/9.3/static/pgupgrade.html
pgupgrade has nothing to do with this: that's just a tool that does in
plac
On Thu, Sep 12, 2013 at 11:21 AM, Raymond O'Donnell wrote:
> On 12/09/2013 17:11, Patrick Dung wrote:
>> By the way, for in-place major version upgrade (not dumping DB and
>> import again), MySQL is doing a better job in here.
>
> http://www.postgresql.org/docs/9.3/static/pgupgrade.html
pgupgrade
On 09/12/2013 09:37 AM, Merlin Moncure wrote:
On Thu, Sep 12, 2013 at 11:21 AM, Raymond O'Donnell wrote:
On 12/09/2013 17:11, Patrick Dung wrote:
By the way, for in-place major version upgrade (not dumping DB and
import again), MySQL is doing a better job in here.
http://www.postgresql.org
From: Thomas Kellerer
To: pgsql-general@postgresql.org
Sent: Friday, September 13, 2013 12:58 AM
Subject: Re: [GENERAL] Major upgrade of PostgreSQL and MySQL
> There is such a list in the release notes:
>
>http://www.postgresql.org/docs/current/static/release-9-3.html#
On 9/12/2013 11:11 AM, Patrick Dung wrote:
> While reading some manual of PostgreSQL and MySQL (eg.
> http://dev.mysql.com/doc/refman/5.1/en/upgrading-from-previous-series.html).
>
> I have found that MySQL has stated many incompatibilities and know
> issues (a long list) in the MySQL version 5.0,
On 12/09/2013 17:11, Patrick Dung wrote:
> By the way, for in-place major version upgrade (not dumping DB and
> import again), MySQL is doing a better job in here.
http://www.postgresql.org/docs/9.3/static/pgupgrade.html
--
Raymond O'Donnell :: Galway :: Ireland
r...@iol.ie
--
Sent via pgsql
33 matches
Mail list logo
