From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
Subject: | Re: Avoid full page images in streaming replication? |
Date: | 2015-10-22 21:42:48 |
Message-ID: | CABUevExEt3y+vOBXzKHNsrfbibKpXmA6d=xj=eyn4PHx7QkBMQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Oct 22, 2015 23:38, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> writes:
> > ISTM it should be possible to avoid sending full page writes to a
> > streaming replica once the replica has reached a consistent state. I
> > assume that the replica would still need to write full pages to it's
> > disk in case of a crash, but the sender could insert special WAL records
> > to tell it when to do so, instead of sending the full page image.
> > Presumably this would be a big win for replication over a WAN.
>
> How are you going to make that work without LSNs in the WAL received by
> the replica diverging from those in the master's WAL?
>
We could in theory send a "this would be been a fpi but it's skipped"
record which would only exist in streaming and just make the standby write
a noop of some kind? It would still be on the standby but it would at least
not consume the bandwidth. Just skip sending the actual contents of the
fpi.
/Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2015-10-22 21:49:28 | Re: Making tab-complete.c easier to maintain |
Previous Message | Pavel Stehule | 2015-10-22 21:42:29 | Re: [PATCH] SQL function to report log message |