Re: Reducing output size of nodeToString - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Reducing output size of nodeToString
Date
Msg-id c48030b4-bb27-4bb0-86f4-0b062f51670c@eisentraut.org
Whole thread Raw
In response to Re: Reducing output size of nodeToString  (Matthias van de Meent <boekewurm+postgres@gmail.com>)
Responses Re: Reducing output size of nodeToString
List pgsql-hackers
On 30.01.24 12:26, Matthias van de Meent wrote:
>> Most of the other defaults I'm doubtful about.  First, we are colliding
>> here between the goals of minimizing the storage size and making the
>> debug output more readable.
> I've never really wanted to make the output "more readable". The
> current one is too verbose, yes.

My motivations at the moment to work in this area are (1) to make the 
output more readable, and (2) to reduce maintenance burden of node 
support functions.

There can clearly be some overlap with your goals.  For example, a less 
verbose and less redundant output can ease readability.  But it can also 
go the opposite direction; a very minimalized output can be less readable.

I would like to understand your target more.  You have shown some 
figures how these various changes reduce storage size in pg_rewrite. 
But it's a few hundred kilobytes, if I read this correctly, maybe some 
megabytes if you add a lot of user views.  Does this translate into any 
other tangible benefits, like you can store more views, or processing 
views is faster, or something like that?




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: make dist using git archive
Next
From: vignesh C
Date:
Subject: Re: Improve eviction algorithm in ReorderBuffer