From: | Poul Kristensen <bcc5226(at)gmail(dot)com> |
---|---|
To: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: FSM corruption and standby servers |
Date: | 2016-11-01 19:31:26 |
Message-ID: | CAAOuvVpv7HsVmry3f+8ZBFm_dzRi0U8vb2QkZxx19KnYohgCqA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
If or when I get a successfull installation containing the abovementioned
components in 24/7 operation I
will try to contribute to your documentation. Before that I would
appreciate if one of you kind people
would review the solution. The cluster(OS) design I intend to get rewieved
by Redhat to be sure of zero faulttolerant.
Thanks.
Poul
2016-10-31 22:46 GMT+01:00 Poul Kristensen <bcc5226(at)gmail(dot)com>:
> I have some comments to the documentation.
>
> I worked with PostgreSQL for some time ago( 5-8 years) setting up a few
> Postgres databases using version 8.4 and RHEL 5:* in production and still
> running.
> A LOT have happened since then and I am going to setup Postgres 9+ with
> everything needed to secure data, backup(PITR)
> , cluster with zero dataloss. OS is RHEL 7.2.
> I my opinion the documentation is not very straightforward with examples
> omn exactly how to make such a complete installation using
> 2+ servers to make data available 24/7. One has to pick up a little here
> and a litte there. And one always have to do a litte there and here to make
> things switch
> in order to make data available 24/7.
> Creating of tablespace can't be scriptet, Restore(I know this another
> list(pg_rman) can't handle symbolic links.
> Sorry about my belching as vocabulary and my bad english!
>
> /Poul
>
>
>
>
> 2016-10-31 19:19 GMT+01:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>
>> "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
>> > On Mon, Oct 31, 2016 at 9:55 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> >> I would have thought that the referenced page is clear enough about
>> >> needing to check the standbys; do you think it isn't?
>>
>> > I can see how the following is a bit loose for someone not
>> super-familiar
>> > with WAL.
>>
>> Yeah. On the other hand, I don't want people who aren't running
>> replication to stop reading as soon as they see something about standby
>> servers. I tweaked the existing wording a bit to emphasize that standbys
>> can be corrupt even with a valid master; hopefully that's enough.
>>
>> regards, tom lane
>>
>>
>> --
>> Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-admin
>>
>
>
>
> --
> Med venlig hilsen / Best regards
> Poul Kristensen
> Linux-OS/Virtualizationexpert and Oracle DBA
>
--
Med venlig hilsen / Best regards
Poul Kristensen
Linux-OS/Virtualizationexpert and Oracle DBA
From | Date | Subject | |
---|---|---|---|
Next Message | Phil Frost | 2016-11-02 19:31:44 | Replica lag, high read IO, vacuum index scanning bug? |
Previous Message | Eloy Coto Pereiro | 2016-11-01 17:25:56 | Issues with WAL Timelines on follower |