From: pgorg_aav <kahitarich-postgresorg@yahoo.com>
To: Jerry Sievers <gsievers19@comcast.net>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: streaming replication sent location not advancing - feature request?
Date: Mon, 10 Mar 2014 07:17:46 -0700 (PDT)
Message-ID: <1394461066.49064.YahooMailNeo@web120303.mail.ne1.yahoo.com> (raw)
In-Reply-To: <86wqg6os2k.fsf@jerry.enova.com>
References: <1394153429.37920.YahooMailNeo@web120301.mail.ne1.yahoo.com>
<86wqg6os2k.fsf@jerry.enova.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Thank you for your response.
I'm following the hybrid model - one thing I've noticed is when the standbys fall back to WAL shipping, they stop taking read requests (in this case we would've lose almost half the capacity), is there something that I can do to prevent that?
The wal_keep_segments was slowly increased to 8000 during this issue.
Hence my "feature request?" comment...
Like mysql (advance apologies for mentioning it :) ) has a slave_io_thread, can one be implemented natively in PostgreSQL?
Or is that left to the individual to implement in the restore_command.
I'm going to try to play around more with the restore command.
Thanks,
Amit
On Friday, March 7, 2014 12:12 PM, Jerry Sievers <gsievers19@comcast.net> wrote:
pgorg_aav <kahitarich-postgresorg@yahoo.com> writes:
>
>> Hi,
>>
>> With wal shipping it is possible to pull the WAL files in advance from the master.
>> Is it possible to do something similar for streaming replication?
>
>wal_keep_segments <something higher>
>
>Otherwise just use the already supported hybrid of WAL archiving and
>streaming.
>
>> This morning due to VM hardware issues, a couple of standbys lagged (A LOT) behind master
>>
>> # select * from pg_stat_replication ;
>> pid | usesysid | usename | application_name | client_addr | client_hostname | client_port | backend_start | state | sent_location |
>> write_location | flush_location | replay_location | sync_priority | sync_state
>> -------+----------+----------+------------------+---------------+-----------------+-------------+-------------------------------+-----------+---------------+----------------+----------------+-----------------+---------------+------------
>> ...=x8 snipped
>> 1758 | 10 | postgres | walreceiver | 172.26.149.47 | | 34798 | 2014-02-04 14:48:51.318344-05 | streaming | 1D0/C49A9BE0 | 1D0/
>> C49A9BE0 | 1D0/C49A9BE0 | 1D0/C49A9B38 | 0 | async
>> 16072 | 10 | postgres | walreceiver | 172.26.115.48 | | 57152 | 2013-12-07 09:25:21.713723-05 | streaming | 1C8/11B40000 | 1C8/
>> 119A0000 | 1C8/11900000 | 1C8/117EDAB8 | 0 | async
>> (9 rows)
>>
>> Thanks much in advance,
>> Amit
>>
>
>--
>Jerry Sievers
>Postgres DBA/Development Consulting
>
>e: postgres.consulting@comcast.net
>p: 312.241.7800
>
>
>--
>Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
>To make changes to your subscription:
>http://www.postgresql.org/mailpref/pgsql-admin
>
>
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: kahitarich-postgresorg@yahoo.com, gsievers19@comcast.net
Subject: Re: streaming replication sent location not advancing - feature request?
In-Reply-To: <1394461066.49064.YahooMailNeo@web120303.mail.ne1.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox