Re: pg_upgrade not preserving comments on predefined roles - Mailing list pgsql-hackers

From Chapman Flack
Subject Re: pg_upgrade not preserving comments on predefined roles
Date
Msg-id 60948606.1030301@anastigmatix.net
Whole thread Raw
In response to Re: pg_upgrade not preserving comments on predefined roles  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 05/02/21 19:25, Tom Lane wrote:
> Chapman Flack <chap@anastigmatix.net> writes:
>> I've appended the comments we use for them at $work, anyway.
> 
> IMO these would have to be shortened quite a bit to be friendly for
> "\du+" displays.  I'm not against the concept though.

I'm certainly not wedded to the exact wording we used here.

That said, our particular reason for having them (the bgworker-produced
roles/memberships/permissions graphviz thing) is not meant just for the
eyes of technical staff, but also to be presentable to, say, compliance
folks coming around asking about security provisions. So making the
comments so terse they'd require expansion for such an audience
might kind of defeat that purpose.

In pg_proc there seem to be a handful of things with 80 to 90 character
comments and one (a statistics function) at 111. Could that be taken
for precedent as to reasonable length?

Regards,
-Chap



pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: alter table set TABLE ACCESS METHOD
Next
From: Jeff Davis
Date:
Subject: Re: alter table set TABLE ACCESS METHOD