From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
Cc: | Melanie Plageman <melanieplageman(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Show various offset arrays for heap WAL records |
Date: | 2023-02-01 17:51:58 |
Message-ID: | CA+Tgmob7qR9=TAtsdkg14qXGn+uJBv4m5-sshFCY9H5ETKnwcw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Feb 1, 2023 at 12:47 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> On Wed, Feb 1, 2023 at 5:20 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> > If we're dumping a lot of details out of each WAL record, we might
> > want to switch to a multi-line format of some kind. No one enjoys a
> > 460-character wide line, let alone 46000.
>
> I generally prefer it when I can use psql without using expanded table
> format mode, and without having to use a pager. Of course that isn't
> always possible, but it often is. I just don't think that that's going
> to become feasible with pg_walinspect queries any time soon, since it
> really requires a comprehensive strategy to deal with the issue of
> verbosity.
Well, if we're thinking of making the output a lot more verbose, it
seems like we should at least do a bit of brainstorming about what
that strategy could be.
--
Robert Haas
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Bossart | 2023-02-01 17:58:06 | Re: Weird failure with latches in curculio on v15 |
Previous Message | Ilya Gladyshev | 2023-02-01 17:51:06 | Re: Progress report of CREATE INDEX for nested partitioned tables |