| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com> |
| Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PG_COLOR not mentioned in docs of vacuumlo, oid2name and pgbench |
| Date: | 2020-03-04 13:01:39 |
| Message-ID: | 20200304130139.GN2593@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 04, 2020 at 10:22:26AM +0100, Juan José Santamaría Flecha wrote:
> I think there are a couple tools missing: pg_archivecleanup, pg_ctl,
> pg_test_fsync and pg_upgrade. pg_regress also, but there is nothing to do
> in the documentation with it.
Indeed, true for pg_archivecleanup and pg_test_fsync, but not for
pg_ctl and pg_upgrade. The funny part about pg_ctl is that the
initialization is done for nothing, because nothing is actually logged
with the APIs of logging.c. pg_upgrade uses its own logging APIs,
which have nothing to do with logging.c.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2020-03-04 13:05:30 | Re: PG_COLOR not mentioned in docs of vacuumlo, oid2name and pgbench |
| Previous Message | Michael Paquier | 2020-03-04 12:55:48 | Re: PG_COLOR not mentioned in docs of vacuumlo, oid2name and pgbench |