| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15591: pg_receivewal does not honor replication slots |
| Date: | 2019-01-14 17:57:31 |
| Message-ID: | 20190114175731.GV2528@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Greetings,
* Magnus Hagander (magnus(at)hagander(dot)net) wrote:
> > If this isn't a bug, then is there a way to document it so the end user
> > knows what is going on? Or is there existing documentation I am
> > overlooking? I guess the doc change would need to be in pg_receivelog, if
> > the problem is unique to it.
>
> The backup documentation does list "set up wal archive" before it gets to
> taking the base backup, and I think the intention is "do that first". OTOH,
> it does not mention pg_receivewal at all, so it's definitely not complete.
> There's been discussion of overhauling that one for some time, but nobody's
> gotten around to actually doing it.
Even those who have been interested in improving it have been
discouraged from doing so due to how overly complicated and messy it is,
in part because of the various ways backups can happen today...
Thanks!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-01-14 18:04:23 | Re: BUG #15592: Memory overuse with subquery containing unnest() and set operations (11.x regression) |
| Previous Message | Tom Lane | 2019-01-14 16:57:55 | Re: BUG #15592: Memory overuse with subquery containing unnest() and set operations (11.x regression) |