| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Kasahara Tatsuhito <kasahara(dot)tatsuhito(at)gmail(dot)com> |
| Cc: | torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Get memory contexts of an arbitrary backend process |
| Date: | 2020-09-24 04:01:49 |
| Message-ID: | 20200924040149.GH28585@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Sep 10, 2020 at 09:11:21PM +0900, Kasahara Tatsuhito wrote:
> I think it's fine to have an interface to delete in an emergency, but
> I agree that
> users shouldn't be made aware of the existence or deletion of dump
> files, basically.
Per the CF bot, the number of tests needs to be tweaked, because we
test each entry filtered out with is_deeply(), meaning that the number
of tests needs to be updated to reflect that if the filtered list is
changed:
t/010_pg_basebackup.pl ... 104/109 # Looks like you planned 109 tests but ran 110.
t/010_pg_basebackup.pl ... Dubious, test returned 255 (wstat 65280, 0xff00)
All 109 subtests passed
Simple enough to fix.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-09-24 04:06:31 | Re: BUG #15383: Join Filter cost estimation problem in 10.5 |
| Previous Message | Pavel Stehule | 2020-09-24 03:58:55 | Re: proposal: schema variables |