| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: allowing wal_level change at run time |
| Date: | 2015-08-19 15:56:22 |
| Message-ID: | 20150819155622.GD10770@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-08-19 17:51:47 +0200, Magnus Hagander wrote:
> That's doable - but what about manual base backups? And if they don't go
> away, what about the ones that are generated by the
> nightly/weekly/hourly/whatever "pg_basebackup -x" ones?
Good questions. I guess we could just make do_pg_start_backup() elevate
the WAL level (using a fixed slot name or some other mechanism) he first
time they're run, until there's explicit admin action.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-08-19 16:46:35 | Badly broken logic in plpython composite-type handling |
| Previous Message | Magnus Hagander | 2015-08-19 15:51:47 | Re: allowing wal_level change at run time |