I have a couple of questions about how streaming replication works in the presence of a high timeout for query cancellation: 1. Where is the WAL data stored while waiting for the query cancellation, the primary or the secondary? In case of a crashduring this interval, could the secondary end up behind the primary due to the WAL data not having been sent over? 2. Can a very high query cancellation value run afoul of wal_keep_segments, or will the primary (assuming it's the one doingthe storing) keep that data around until the query completes or is cancelled? Thanks! -- -- Christophe Pettus xof@thebuild.com
On 8/1/12, Christophe Pettus <xof@thebuild.com> wrote: > I have a couple of questions about how streaming replication works in the > presence of a high timeout for query cancellation: Are you referring to queries on the slave? The master doesn't know what the slave is doing, so it would keep on shipping streaming replication data. -- Mike Nolan
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера