| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Devrim Gündüz <devrim(at)gunduz(dot)org> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_basebackup against older server versions |
| Date: | 2019-03-06 09:09:45 |
| Message-ID: | 20190306090945.GK30982@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 06, 2019 at 11:55:12AM +0300, Devrim Gündüz wrote:
> Apologies if this has been discussed before: When I run pg_basebackup in git
> head against v11 server, it treats v11 as v12: Does not create recovery.conf,
> adds recovery parameters to postgresql.auto.conf, and also creates
> standby.signal file. Is this expected, or a bug?
You are right, this is a bug. Compatibility with past server versions
should be preserved, and we made an effort to do so in the past (see
the switch to pg_wal/ for example). Fortunately, maintaining the
compatibility is simple enough as the connection information is close
by so that we just need to change postgresql.auto.conf to
recovery.conf, and avoid the creation of standby.signal.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2019-03-06 09:33:02 | bug in update tuple routing with foreign partitions |
| Previous Message | Ashwin Agrawal | 2019-03-06 08:58:23 | Re: Make drop database safer |