On Fri, Mar 14, 2025 at 12:50 PM Greg Sabino Mullane
wrote:
> I'd rather not sit on this another year, if we can help it. We really
> should be warning people about this practice. The exact wording of the hint
> can be up for debate (or postponed - we technically don't have to say
> anything othe
On Sat, Mar 15, 2025 at 2:27 PM Lateef Sagar wrote:
> Hello devs,
> I am a coding enthusiast. I have downloaded code in a Ubuntu VMWare
> machine and I am able to compile the code.
>
> I am looking for a course / site that can give me an overview of the code
> like:
> 1. How is the code organized
On Fri, Oct 4, 2024 at 10:08 AM Greg Sabino Mullane
wrote:
> Congratulations to all! This seems the sort of thing we should crosspost
> to -general and/or -announce, no?
>
>
Congratulations to all!
+1 on Greg's suggestion.
Roberto
On Fri, Sep 27, 2024 at 8:07 AM Greg Sabino Mullane
wrote:
> tl;dr let's assume SSDs are popular and HDDs are the exception and flip
> our default
>
> Granted, there are other factors involved, and yes, perhaps we should
> tweak some of the similar settings as well, but ranom_page_cost is the
On Sun, Sep 22, 2024 at 8:10 AM Marcos Pegoraro wrote:
> Em sáb., 21 de set. de 2024 às 18:42, Bruce Momjian
> escreveu:
>
>> I suggest you explain what changes would make the docs better (meaing
>> more useful).
>>
>
> So, if we have a "Compatibility/Translation/Feature Comparison/ ... with
> o
On Fri, Sep 20, 2024 at 11:43 AM Marcos Pegoraro wrote:
>
> My suggestion is: Postgres DOCs are written and have to be read by
> Postgres users, just that. If you are Oracle user, search for a tutorial on
> how to migrate to Postgres or find tools for it, but not in DOCs
>
As Tomas, Tom and othe
On Fri, Apr 26, 2024 at 5:54 AM Jonathan S. Katz
wrote:
> The Core Team would like to extend our congratulations to Melanie
> Plageman and Richard Guo, who have accepted invitations to become our
> newest PostgreSQL committers.
>
> Please join us in wishing them much success and few reverts!
>
A
On Wed, Feb 28, 2024 at 11:55 AM David E. Wheeler
wrote:
>
> IME the keys to decent-looking Markdown are:
>
> 1. Wrapping lines to a legible width (76-80 chars)
> 2. Link references rather than inline links
+1 on Markdown including David's suggestions above. Agree that without
proper guidelines
On Mon, Mar 18, 2024 at 10:12 AM Robert Haas wrote:
> I was looking at the documentation index this morning[1], and I can't
> help feeling like there are some parts of it that are over-emphasized
> and some parts that are under-emphasized. I'm not sure what we can do
> about this exactly, but I t
On Fri, Jan 12, 2024 at 3:15 PM Cary Huang wrote:
> I think it is good to warn the user about the increased allocation of
> memory for certain parameters so that they do not abuse it by setting it to
> a huge number without knowing the consequences.
>
> It is true that max_connections can increas
Suggestion:
In the C example you added you mention in the comment:
+ /* Methods from TableAmRoutine omitted from example, but all
+ non-optional ones must be provided here. */
Perhaps you could provide a "see " to point the reader finding your
example where he could find these non-optional
allocation of those resources, including shared memory.
Sincerely,
Roberto Mello
max-connections-guc-detail.patch
Description: Binary data
On Mon, Oct 30, 2023 at 1:09 AM Michael Paquier wrote:
>
> I have been reviewing the patch, and applied portions of it as of
> dc5bd388 and 1ffdc03c and they're quite independent pieces. After
> that, the remaining bits of the patch to change the behavior is now
> straight-forward. I have writt
Adding to this thread as suggested by jkatz for consideration of
adding to release notes...
In [1] I mention the omission of ldap_password_hook and a suggested paragraph.
Roberto
[1]
https://www.postgresql.org/message-id/CAKz%3D%3DbLzGb-9O294AoZHqEWpAi2Ki58yCr4gaqg1HnZyh3L1uA%40mail.gmail.com
On Tue, Jun 27, 2023 at 11:40 AM Jonathan S. Katz wrote:
>
> Was this discussed on the release notes thread?[1]. It can always be
> added to the release notes -- those aren't finalized until GA.
>
> After Beta 1, the announcements are either about new feature
> additions/removals since the last be
On Tue, Jun 27, 2023 at 8:32 AM Jonathan S. Katz wrote:
>
> I used the open items list[1] to build the draft. If there are any
> notable please omissions, please let me know.
I noticed that ldap_password_hook [1] was omitted from the release
notes. I believe it should be included if nothing else
On Fri, Apr 28, 2023 at 12:10 PM Gautham Raj
wrote:
> Thank you for the quick response.
>
> Yes, I'm willing to get the latest version. I read some articles CentOS 7
> doesn't support the latest versions. So was trying the old versions.
>
> I tried the article shared but, got the below error at t
On Tue, Mar 21, 2023 at 9:35 AM Jonathan S. Katz wrote:
>
> You can track open items for the PostgreSQL 16 release here:
>
> https://wiki.postgresql.org/wiki/PostgreSQL_16_Open_Items
The wiki page references April 8th, 2022, btw.
Roberto
On Tue, Jul 5, 2022 at 5:47 AM Alvaro Herrera
wrote:
> OK, I have adopted all your proposed changes, thanks for submitting in
> both forms. I did some more wordsmithing and pushed, to branches 12 and
> up. 11 fails 'make check', I think for lack of Docbook id tags, and I
> didn't want to waste
On Mon, Jul 4, 2022 at 9:20 AM Alvaro Herrera
wrote:
>
> [Some of] these additions are wrong actually. It says that autovacuum
> will not summarize new entries; but it does. If you just let the table
> sit idle, any autovacuum run that cleans the table will also summarize
> any ranges that need
On Fri, Jul 1, 2022 at 5:00 PM Nathan Bossart
wrote:
>
>
> That being said, I don't see why this information couldn't be provided in a
> system view. IMO it is generically useful.
+1 for a system view with appropriate permissions, in addition to the
hooks.
That would make the information easi
Here's a patch to clarify the BRIN indexes documentation, particularly with
regards
to autosummarize, vacuum and autovacuum. It basically breaks down a big
blob of a
paragraph into multiple paragraphs for clarity, plus explicitly tells how
summarization
happens manually or automatically.
I also ad
On Sat, Jun 4, 2022 at 5:23 PM Tomas Vondra
wrote:
> Hi,
>
> At on of the pgcon unconference sessions a couple days ago, I presented
> a bunch of benchmark results comparing performance with different
> data/WAL block size. Most of the OLTP results showed significant gains
> (up to 50%) with smal
On Thu, Jun 10, 2021 at 1:27 AM David Rowley wrote:
>
> I think we should change all 55 instances of "a SQL" in the docs to
> use "an SQL" and leave the 800 other instances of "a SQL" alone.
+1
Consistency is good.
Roberto
24 matches
Mail list logo
