An improved README experience for PostgreSQL

;s missing. If there's any kind of feedback or consensus on this thread, I'm happy to create and send a patch. Thanks for taking a look! Andrew Atkinson w/ reviews from Samay Sharma

Re: An improved README experience for PostgreSQL

Thanks for the feedback Nathan and Tom. Samay also suggested adding the patch. I've added a .patch with the file for consideration. On Mon, Feb 26, 2024 at 2:30 PM Tom Lane wrote: > Nathan Bossart writes: > > I think this would be nice. If the Markdown version is reasonably > readable > > as p

Re: Add publisher and subscriber to glossary documentation.

If there's a movement towards "node" to refer to the database which has the Subscription object, then perhaps the documentation for 31.2. Subscription, Chapter 31. Logical Replication should be updated as well, since i

Re: An improved README experience for PostgreSQL

I've grabbed Nathan's patch, and pushed it to GitHub simply to preview the rendered Markdown there. This isn't intended to be reviewed, this is just for anyone else that's interested in easily seeing the HTML version of the Markdown file compared with the earlier one. Nathan's direct conversion: h

Re: An improved README experience for PostgreSQL

600, Nathan Bossart wrote: > > On Wed, Feb 28, 2024 at 02:07:34PM -0600, Andrew Atkinson wrote: > >> I agree that starting with the direct conversion is reasonable. Markdown > >> "modernizes" the file using a popular plain text file format that's > >> re

Re: [PATCH] pgbench log file headers

2700 0 2 1130 0 1699902315 903973 ... The generated pgbench_log.62387 log file showed headers "client_id transaction_no time script_no time_epoch time_us". Hope that helps with your patch acceptance journey. Good luck! Andrew Atkinson On Mon, Nov 13, 2023 at 11:55 AM Adam Hend

Re: Doc: Minor update for enable_partitionwise_aggregate

Thank you for the feedback and clarifications Ashutosh. How about this? "which allows grouping or aggregation on partitioned tables to be performed separately for each partition." Attached a v2 patch file with this change. Here is a gist w/ a partitioned table and 2 partitions, comparing executi

[Doc] Glossary Term Definitions Edits

to “There are two secondary forks” I was able to build the documentation locally and preview the HTML version. If these types of changes are helpful, and can continue a consistent style through all the terms and provide a new (larger) v2 patch. Thanks for taking a look. Andrew Atkinson

Re: [Doc] Glossary Term Definitions Edits

why I’m wrong. :) - Space in data pages which does not contain current row versions, + Space in data pages that does not contain current row versions, Smaller patch attached! Thanks. On Sat, Oct 14, 2023 at 12:55 AM Erik Wienhold wrote: > On 2023-10-14 06:16 +0200, Andre

Re: DROP CONSTRAINT, printing a notice and/or skipping when no action is taken

Oof, the subject line was meant to be DROP DEFAULT, not constraint On Thu, Feb 13, 2025 at 11:13 AM Andrew Atkinson wrote: > Hello. I noticed a small opportunity for a possible enhancement to DROP > DEFAULT, and wanted to share the idea. Apologies if this idea was suggested > before

DROP CONSTRAINT, printing a notice and/or skipping when no action is taken

Hello. I noticed a small opportunity for a possible enhancement to DROP DEFAULT, and wanted to share the idea. Apologies if this idea was suggested before, I tried a basic search for pgsql-hackers similar things but didn’t find a hit. I noticed when running an ALTER TABLE with DROP DEFAULT, wheth