From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Server-side base backup: why superuser, not pg_write_server_files? |
Date: | 2022-02-02 18:44:18 |
Message-ID: | CA+Tgmoba-3Uf5KiCF3Qa6V0BnyMWhCB4a2ND5_euTsO=3EszPQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Feb 2, 2022 at 12:55 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> > This seems like a good idea, but I'm not going to slip a change from
> > an exact test count to done_testing() into a commit on some other
> > topic...
>
> Actually, it seemed that the consensus in the nearby thread [1]
> was to start doing exactly that, rather than try to convert them
> all in one big push.
Urk. Well, OK then.
Such an approach seems to me to have essentially nothing to recommend
it, but I just work here.
--
Robert Haas
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-02-02 18:46:39 | Re: Server-side base backup: why superuser, not pg_write_server_files? |
Previous Message | Robert Haas | 2022-02-02 18:42:55 | Re: archive modules |