Re: Combine pg_walinspect till_end_of_wal functions with others

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Jeff Davis <pgsql(at)j-davis(dot)com>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Combine pg_walinspect till_end_of_wal functions with others
Date: 2023-03-16 07:18:12
Message-ID: ZBLCtGb/V/hSs6SH@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 15, 2023 at 06:50:01PM +0900, Michael Paquier wrote:
> This is a duplicate of what describe.c uses, with a COLLATE clause.
> The main goal was to have a simple check, so I'd still stand by the
> simplest choice and move on.

Please note that I have done something about that with e643a31 by
replacing the problematic \dx with a SELECT query, but left the second
one as it should not be a problem.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2023-03-16 07:38:07 Re: logical decoding and replication of sequences, take 2
Previous Message Michael Paquier 2023-03-16 07:13:14 Re: [PATCH] Tracking statements entry timestamp in pg_stat_statements