| 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:58:15 |
| Message-ID: | CA+TgmobA=RLsZfcpcr+Y13DzQApSFz1QuPGPBGMvRAQVrRb4zQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 2, 2022 at 1:50 PM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Wed, Feb 2, 2022 at 1:46 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > Well, if someone wants to step up and provide a patch that changes 'em
> > all at once, that'd be great. But we've discussed this before and
> > nothing's happened.
>
> I mean, I don't understand why it's even better. And I would go so far
> as to say that if nobody can be bothered to do the work to convert
> everything at once, it probably isn't better.
And one thing that concretely stinks about is the progress reporting
you get while the tests are running:
t/010_pg_basebackup.pl ... 142/?
That's definitely less informative than 142/330 or whatever.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2022-02-02 19:36:11 | Re: Server-side base backup: why superuser, not pg_write_server_files? |
| Previous Message | Robert Haas | 2022-02-02 18:50:17 | Re: Server-side base backup: why superuser, not pg_write_server_files? |