Re: Can we delete the vacuumdb.sgml notes about which version each option was added in?

2023-04-16 Thread David Rowley
On Mon, 17 Apr 2023 at 02:29, Tom Lane wrote: > But +1 for just dropping them. Thanks. I just pushed the patch to drop them all. David

Re: Can we delete the vacuumdb.sgml notes about which version each option was added in?

2023-04-16 Thread Tom Lane
Justin Pryzby writes: > On Sun, Apr 16, 2023 at 10:14:35PM +1200, David Rowley wrote: >> Does anyone think we should keep these? > I don't know if I'd support removing the notes, but I agree that they > don't need to take up anywhere near as much space as they do (especially > since the note is

Re: Can we delete the vacuumdb.sgml notes about which version each option was added in?

2023-04-16 Thread Justin Pryzby
On Sun, Apr 16, 2023 at 10:14:35PM +1200, David Rowley wrote: > I was just looking at the vacuumdb docs and noticed that I had > neglected to follow the tradition of adding a note to mention which > version we added the new option in when I committed the > --buffer-usage-limit patch. > > There

Re: Can we delete the vacuumdb.sgml notes about which version each option was added in?

2023-04-16 Thread Nathan Bossart
On Sun, Apr 16, 2023 at 10:14:35PM +1200, David Rowley wrote: > There are 3 notes there that read "This option is only available for > servers running PostgreSQL 9.6 and later.". Since 9.6 is a few years > out of support, can we get rid of these 3? +1 > Or better yet, can we just delete them

Can we delete the vacuumdb.sgml notes about which version each option was added in?

2023-04-16 Thread David Rowley
I was just looking at the vacuumdb docs and noticed that I had neglected to follow the tradition of adding a note to mention which version we added the new option in when I committed the --buffer-usage-limit patch. There are 3 notes there that read "This option is only available for servers