On Fri, Feb 22, 2019 at 2:03 AM Tom Lane wrote:
> Bruce Momjian writes:
> > On Thu, Feb 21, 2019 at 09:31:32PM -0500, Stephen Frost wrote:
> >> * Bruce Momjian (br...@momjian.us) wrote:
> >>> There was too much concern that users would accidentally start the old
> >>> server at some later point,
Bruce Momjian writes:
> On Thu, Feb 21, 2019 at 09:31:32PM -0500, Stephen Frost wrote:
>> * Bruce Momjian (br...@momjian.us) wrote:
>>> There was too much concern that users would accidentally start the old
>>> server at some later point, and its files would be hard linked to the
>>> new live serv
On Thu, Feb 21, 2019 at 09:31:32PM -0500, Stephen Frost wrote:
> Greetings,
>
> * Bruce Momjian (br...@momjian.us) wrote:
> > On Tue, Feb 19, 2019 at 12:25:24PM -0500, Stephen Frost wrote:
> > > Ah, right, I forgot that it did that, fair enough.
> > >
> > > I've never been thrilled with that part
Greetings,
* Bruce Momjian (br...@momjian.us) wrote:
> On Tue, Feb 19, 2019 at 12:25:24PM -0500, Stephen Frost wrote:
> > Ah, right, I forgot that it did that, fair enough.
> >
> > I've never been thrilled with that particular approach due to the
> > inherent risks of people messing directly with
On Tue, Feb 19, 2019 at 12:25:24PM -0500, Stephen Frost wrote:
> Ah, right, I forgot that it did that, fair enough.
>
> I've never been thrilled with that particular approach due to the
> inherent risks of people messing directly with files like pg_control,
> but that's how it is for now.
There w
Greetings,
* Martín Fernández (fmarti...@gmail.com) wrote:
> On Tue, Feb 19, 2019 at 1:37 PM Stephen Frost wrote:
> > * Martín Fernández (fmarti...@gmail.com) wrote:
> > > Thanks for information! I've refactor our migration scripts to follow
> > the suggestions.
> >
> > Please don't top-post on t
Stephen,
@bilby91
On Tue, Feb 19, 2019 at 1:37 PM Stephen Frost wrote:
> Greetings,
>
> * Martín Fernández (fmarti...@gmail.com) wrote:
> > Thanks for information! I've refactor our migration scripts to follow
> the suggestions.
>
> Please don't top-post on these mailing lists.
>
> > One extra
Greetings,
* Martín Fernández (fmarti...@gmail.com) wrote:
> Thanks for information! I've refactor our migration scripts to follow the
> suggestions.
Please don't top-post on these mailing lists.
> One extra question that popped up. As long as we don't start the standby
> (after running rsync
Stephen,
Thanks for information! I've refactor our migration scripts to follow the
suggestions.
One extra question that popped up. As long as we don't start the standby (after
running rsync), we can always `rm -f $PGDATA_10` and promote the standby if
necessary for failover right ? We also ne
Thank you Stephen 👍
El mar., 19 de feb. de 2019 a la(s) 10:05, Stephen Frost (sfr...@snowman.net)
escribió:
> Greetings,
>
> * Hellmuth Vargas (hiv...@gmail.com) wrote:
> > But could you do the following procedure?:
>
> > pg_upgrade of the master
> > rysnc with a hot standby
>
> The above should
Greetings,
* Hellmuth Vargas (hiv...@gmail.com) wrote:
> But could you do the following procedure?:
> pg_upgrade of the master
> rysnc with a hot standby
The above should be alright provided both the primary and the standby
are down and the instructions in the pg_upgrade docs are followed.
> ar
Hi
But could you do the following procedure?:
pg_upgrade of the master
rysnc with a hot standby
arracar master
hot standby start
stop hot standby and rsync the other hot standby with the migrated hot
standby?
El mar., 19 de feb. de 2019 a la(s) 06:12, Stephen Frost (sfr...@snowman.net)
escribió:
Greetings,
* Martín Fernández (fmarti...@gmail.com) wrote:
> After reading the pg_upgrade documentation multiple times, it seems that
> after running pg_upgrade on the primary instance, we can't start it until we
> run rsync from the primary to the standby. I'm understanding this from the
> fol
Laurenz and Hellmuth, replying to both of you!
Thanks for the quick replies BTW!
Martín
On Mon, Feb 18, 2019 at 5:32 PM Hellmuth Vargas wrote:
>
> Hola Martin
>
> Pues si uno sigue la secuencia de la pagina de ayuda de PostgreSQL
>
> https://www.postgresql.org/docs/10/pgupgrade.html
>
> Usage
Hola Martin
Pues si uno sigue la secuencia de la pagina de ayuda de PostgreSQL
https://www.postgresql.org/docs/10/pgupgrade.html
Usage
(...)
7. Stop both servers
(...)
10. Upgrade Streaming Replication and Log-Shipping standby servers
(...)
12. Start the new server
*The new server can now be sa
Martín Fernández wrote:
> After reading the pg_upgrade documentation multiple times, it seems that
> after running pg_upgrade on the primary instance, we can't start it until we
> run rsync from the primary to the standby. I'm understanding this from the
> following section in the pg_upgrade man
16 matches
Mail list logo
