Re: Get memory contexts of an arbitrary backend process

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kasahara Tatsuhito <kasahara(dot)tatsuhito(at)gmail(dot)com>
Cc: torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Get memory contexts of an arbitrary backend process
Date: 2020-09-03 17:40:07
Message-ID: 640735.1599154807@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Kasahara Tatsuhito <kasahara(dot)tatsuhito(at)gmail(dot)com> writes:
> Yes, but it's not only for future expansion, but also for the
> usability and the stability of this feature.
> For example, if you want to read one dumped file multiple times and analyze it,
> you will want the ability to just read the dump.

If we design it to make that possible, how are we going to prevent disk
space leaks from never-cleaned-up dump files?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2020-09-03 17:59:11 Re: INSERT ON CONFLICT and RETURNING
Previous Message Tom Lane 2020-09-03 17:36:58 Re: Fix for configure error in 9.5/9.6 on macOS 11.0 Big Sur