Re: docs: minor typo fix for "lower(anymultirange)"

On Thu, Apr 25, 2024 at 09:02:34AM +0800, Richard Guo wrote: > Good catch! I checked the descriptions for "upper(anymultirange)", > "lower(anyrange)" and "upper(anyrange)", and they are all correct. We > should fix this one. +1. -- Michael signature.asc Description: PGP signature

Re: docs: minor typo fix for "lower(anymultirange)"

On Thu, Apr 25, 2024 at 8:40 AM Ian Lawrence Barwick wrote: > Hi > > Here: > > > https://www.postgresql.org/docs/current/functions-range.html#MULTIRANGE-FUNCTIONS-TABLE > > the description for "lower(anymultirange)": > > > (NULL if the multirange is empty has no lower bound). > > is missing "or"

docs: minor typo fix for "lower(anymultirange)"

Hi Here: https://www.postgresql.org/docs/current/functions-range.html#MULTIRANGE-FUNCTIONS-TABLE the description for "lower(anymultirange)": > (NULL if the multirange is empty has no lower bound). is missing "or" and should be: > (NULL if the multirange is empty or has no lower bound).

Re: Minor typo in generate_useful_gather_paths comment

On Tue, 6 Jul 2021 at 06:55, James Coleman wrote: > While re-reading this code I found a small typo and fixed it (making > the comment more explicit at the same time). Thanks. Pushed (9ee91cc58). David

Minor typo in generate_useful_gather_paths comment

While re-reading this code I found a small typo and fixed it (making the comment more explicit at the same time). Thanks, James v1-0001-Fix-typo-in-comment.patch Description: Binary data

Re: Minor typo

Greetings, * Kyotaro HORIGUCHI (horiguchi.kyot...@lab.ntt.co.jp) wrote: > At Tue, 4 Dec 2018 11:37:16 -0500, Stephen Frost wrote > in <20181204163716.gr3...@tamriel.snowman.net> > > Thanks to everyone for sharing their thoughts here, the goal is simply > > to try and have the comments as clear a

Re: Minor typo

At Tue, 4 Dec 2018 11:37:16 -0500, Stephen Frost wrote in <20181204163716.gr3...@tamriel.snowman.net> > Thanks to everyone for sharing their thoughts here, the goal is simply > to try and have the comments as clear as we can for everyone. > > Please find attached a larger rewording of the commen

Re: Minor typo

Greetings, * Kyotaro HORIGUCHI (horiguchi.kyot...@lab.ntt.co.jp) wrote: > At Wed, 28 Nov 2018 10:01:36 +0900, Michael Paquier > wrote in <20181128010136.gu1...@paquier.xyz> > > On Tue, Nov 27, 2018 at 07:51:03PM -0500, Stephen Frost wrote: > > > That isn't at all what I got from that. > > > > >

Re: minor typo in dsa.c

On Thu, Nov 29, 2018 at 1:40 PM Ideriha, Takeshi wrote: > I found a minor typo in dsa.c. > > s/set_dsa_size_limit/dsa_set_size_limit/ Thanks! Pushed. -- Thomas Munro http://www.enterprisedb.com

minor typo in dsa.c

Hi. I found a minor typo in dsa.c. s/set_dsa_size_limit/dsa_set_size_limit/ regards, == Takeshi Ideriha Fujitsu Limited 0001-Minor-typo-in-dsa.c.patch Description: 0001-Minor-typo-in-dsa.c.patch

Re: Minor typo

This is a noise from a Japanese having poor English skill.. At Wed, 28 Nov 2018 10:01:36 +0900, Michael Paquier wrote in <20181128010136.gu1...@paquier.xyz> > On Tue, Nov 27, 2018 at 07:51:03PM -0500, Stephen Frost wrote: > > That isn't at all what I got from that. > > > > A rewrite of this rea

Re: Minor typo

On Tue, Nov 27, 2018 at 07:51:03PM -0500, Stephen Frost wrote: > That isn't at all what I got from that. > > A rewrite of this really should avoid talking about removing the hole as > if it's 'compression' because, first of all, it isn't, and second, now > that we have *actual* compression happeni

Re: Minor typo

Greetings, * Michael Paquier (mich...@paquier.xyz) wrote: > On Tue, Nov 27, 2018 at 07:18:39PM -0500, Tom Lane wrote: > > * When wal_compression is enabled and a "hole" is removed from a full > > * page image, the page image is compressed using PGLZ compression. > > > > (BTW, is this trying t

Re: Minor typo

Greetings, * Tom Lane (t...@sss.pgh.pa.us) wrote: > Daniel Gustafsson writes: > >> On 28 Nov 2018, at 00:43, Stephen Frost wrote: > >> Sending it here in case anyone feels that we should do more than just > >> correct the word..? Perhaps for non-native English speakers seeing > >> "whose" used

Re: Minor typo

On Tue, Nov 27, 2018 at 07:18:39PM -0500, Tom Lane wrote: > * When wal_compression is enabled and a "hole" is removed from a full > * page image, the page image is compressed using PGLZ compression. > > (BTW, is this trying to say that we don't apply compression if the page > contains no hole?

Re: Minor typo

Daniel Gustafsson writes: >> On 28 Nov 2018, at 00:43, Stephen Frost wrote: >> Sending it here in case anyone feels that we should do more than just >> correct the word..? Perhaps for non-native English speakers seeing >> "whose" used here is confusing? > Being a non-native English speaker I th

Re: Minor typo

> On 28 Nov 2018, at 00:43, Stephen Frost wrote: > Sending it here in case anyone feels that we should do more than just > correct the word..? Perhaps for non-native English speakers seeing > "whose" used here is confusing? Being a non-native English speaker I think it’s fine and, in my own bia

Minor typo

Greetings, While reviewing a bit of code around full page images, I came across a typo and fixed it in the attach. Sending it here in case anyone feels that we should do more than just correct the word..? Perhaps for non-native English speakers seeing "whose" used here is confusing? If I don't