Typo in range types documentation
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/18/rangetypes.html Description: It looks to me as if there is an error in the sample associated with documentation on date ranges on page: https://www.postgresql.org/docs/current/rangetypes.html If you scroll to the last few examples on the page, the values inserted are in [) brackets rather than [] brackets.
Re: Document default values for --fsync-interval and --plugin in pg_recvlogical
On Mon, Nov 17, 2025 at 3:34 AM Laurenz Albe wrote: > > On Sun, 2025-11-16 at 15:19 +0900, Fujii Masao wrote: > > I noticed that pg_recvlogical --help shows default values for > > the --fsync-interval and --plugin options, but the docs does not. > > This would be inconvenient for users. > > > > The attached patch adds the missing default value descriptions > > to the pg_recvlogical docs. > > +1 for that patch, it looks good to me. Thanks for the review! I've pushed the patch. Regards, -- Fujii Masao
Re: Typo in range types documentation
On Mon, Nov 17, 2025 at 8:34 AM PG Doc comments form
wrote:
> It looks to me as if there is an error in the sample associated with
> documentation on date ranges on page:
> https://www.postgresql.org/docs/current/rangetypes.html
> If you scroll to the last few examples on the page, the values inserted are
> in [) brackets rather than [] brackets.
Do you mean the room_reservation table? A tsrange uses [) syntax,
signifying closed/open endpoints. So it includes the start time but
not the end time. This is the most common way to use ranges, since it
lets adjacent ranges "lock together" without any overlap.
You can input tsranges with whatever endpoints you like, but they will
use [) syntax when they draw themselves. You can define new range
types with different behavior though. See
https://www.postgresql.org/docs/18/rangetypes.html#RANGETYPES-DISCRETE
Yours,
--
Paul ~{:-)
[email protected]
