; when we are already talking
about function definitions?/
I agree that it may seem redundant, I added "function" here for the sake of
consistency with lines 1829/1830 (if applied to the master branch)
where the documentation mentions "standard internal*function* library".
Please,
Dear all,
I have prepared a patch containing some minor inconsistencies in the
documentation. Please, take a look.
I will be looking forward to your feedback.
The patch shall be applied to the REL_18_STABLE branch.
--
Regards,
Oleg Sibiryakov
Technical Writer
Postgres Professional, The
your consideration.
--
Regards,
Oleg Sibiryakov
Technical Writer
Postgres Professional, The Russian Postgres Company
https://postgrespro.ru
On 10.09.2025 10:54, Oleg wrote:
Dear all,
I have prepared a patch containing some minor inconsistencies in the
documentation. Please, take a look.
I
Dear Daniel,
Thank you for your prompt feedback.
Attached, please find the updated documentation patch, which
incorporates your suggestions from both the first and second rounds of
review.
--
Oleg Sibiryakov
On 22.10.2025 11:02, Daniel Gustafsson wrote:
On 13 Oct 2025, at 12:51, Oleg
Dear Daniel,
Could you please provide your feedback on the last two points?
Once I have it, I will send the updated patch immediately to finalize
the improvements.
Thank you,
Oleg
On 13.10.2025 13:51, Oleg wrote:
Thank you for your feedback, Daniel.
My thoughts are below:
/- Change the
feedback.
The patch shall be applied to the REL_17_STABLE branch.
--
Regards,
Oleg Sibiryakov
Technical Writer
Postgres Professional, The Russian Postgres Company
https://postgrespro.ru
diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml
index a63cc71efa2..7a905fd6a3a 100644
--- a/doc
Thank you for your feedback.
1. Since we do not want to use here, I suggest we hyphenate it
as "built-in". What's your take on it?
2. Leaving not-null is fine.
--
Oleg Sibiryakov
On 06.09.2024 16:20, Daniel Gustafsson wrote:
On 5 Sep 2024, at 11:33, Oleg Sibiryakov wrot
value).
So I do think we cannot really leave it as is.
--
Oleg Sibiryakov
On 11.09.2024 12:53, Peter Eisentraut wrote:
On 10.09.24 15:02, Daniel Gustafsson wrote:
On 10 Sep 2024, at 13:46, Oleg Sibiryakov
wrote:
1. Since we do not want to use here, I suggest we
hyphenate it as "bui
On Thu, Jan 11, 2018 at 7:22 PM, Bruce Momjian wrote:
> On Tue, Oct 24, 2017 at 08:18:49PM +, [email protected] wrote:
>> The following documentation comment has been logged on the website:
>>
>> Page: https://www.postgresql.org/docs/10/static/acronyms.html
>> Description:
>>
>> Hello al
On Sat, Feb 24, 2018 at 4:04 AM, Peter Eisentraut
wrote:
> On 2/23/18 11:21, Tom Lane wrote:
>> In the distant
>> past, as I recall, we had a GIF or two; but we abandoned that on the
>> grounds that it was unmaintainable and also incompatible with some
>> documentation output formats. I'm not too
On Mon, Feb 26, 2018 at 10:23 PM, Tom Lane wrote:
> Craig Ringer writes:
>> On 26 February 2018 at 12:16, Tom Lane wrote:
>>> How can we resolve these issues?
>
>> Question the assumptions and requirements. Why do we actually _need_
>> diffable, mergeable images? Sure, it'd be *nice*, but what's
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
On Wed, Apr 4, 2018 at 12:59 PM, PG Doc comments form
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/10/static/ltree.html
> Description:
>
> Hi,
On Wed, Apr 4, 2018 at 8:17 PM, Alvaro Herrera wrote:
> David G. Johnston wrote:
>
>> I'm not seeing the value in providing a link, especially one that we don't
>> control, here. Futhermore, we could probably drop the whole "In
>> practice..." sentence. But if not at least put a period after "li
Hi there,
Attached is a small patch, which documents the maximum size of
json[b] types. Probably, it's worth to patch previous releases, where
the types were introduced.
Best regards,
Oleg
--
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
json.sgml.
On Wed, Apr 25, 2018 at 2:12 AM, Tom Lane wrote:
> Oleg Bartunov writes:
>> Attached is a small patch, which documents the maximum size of
>> json[b] types. Probably, it's worth to patch previous releases, where
>> the types were introduced.
>
> If you said &q
On Wed, Apr 25, 2018 at 6:50 PM, Oleg Bartunov wrote:
> On Wed, Apr 25, 2018 at 2:12 AM, Tom Lane wrote:
>> Oleg Bartunov writes:
>>> Attached is a small patch, which documents the maximum size of
>>> json[b] types. Probably, it's worth to patch previous re
Hi,
Please, consider attached patch, which improves contrib/bloom documentation.
Best regards,
Oleg
--
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
bloom.sgml.patch
Description: Binary data
On Mon, Oct 15, 2018 at 12:48 AM Thomas Munro
wrote:
>
> On Mon, Oct 15, 2018 at 10:15 AM Oleg Bartunov
> wrote:
> > Please, consider attached patch, which improves contrib/bloom documentation.
>
> Hello Oleg, I have no comment on the technical details but here is
> s
On Sun, Oct 21, 2018 at 11:24 PM Tom Lane wrote:
>
> Oleg Bartunov writes:
> > The commit 9b5c8d45f62bd3d243a40cc84deb93893f2f5122 is now 10+ years
> > old, may be we could remove deprecated @@@ operator ?
>
> Is it actually causing any problem? AFAICS it's just
On Wed, Nov 28, 2018 at 8:33 PM Jürgen Purtz wrote:
>
> After one week no response at all? Neither positive nor negative. It seems
> that the community has little interest in the SVG issue. Or in my suggestion?
First of all, I am BIG + for having diagrams in our documentation.
I once estimated
On Thu, Nov 29, 2018 at 5:40 AM Stephen Frost wrote:
>
> Greetings,
>
> * Michael Paquier ([email protected]) wrote:
> > On Wed, Nov 28, 2018 at 11:00:31AM +, PG Doc comments form wrote:
> > > For the archive command:
> > > <=128 There are not errors in the PostgreSQL log (messages with seve
I noticed that in our docs for PG12 there is no SQL-2016, but we actually
have JSON Path implementation committed, which is a part of SQL-2016
standard. One missing feature - is datetime support. Peter, will you
add this or I prepare the patch ?
Oleg
--
Postgres Professional: http
On Mon, May 27, 2019 at 2:33 PM Peter Eisentraut
wrote:
>
> On 2019-05-12 10:14, Oleg Bartunov wrote:
> > I noticed that in our docs for PG12 there is no SQL-2016, but we actually
> > have JSON Path implementation committed, which is a part of SQL-2016
> > standard.
On 2 Jul 2019, at 11:13, Jürgen Purtz wrote:
After the integration of figures into the documentation it may be helpful
to extent the TOC with a 'List of Figures'. Any opinion?
If yes: The same for 'List of Tables' and 'List of Examples'?
There is a simple way to enable this feature: change line
Thank you, Daniel.
--
Oleg Sibiryakov
On 02.10.2024 15:58, Daniel Gustafsson wrote:
On 2 Oct 2024, at 10:09, Oleg Sibiryakov wrote:
Thank you for your kind feedback! I will take due note of the comments in the
next documentation patches as well.
I have made all the changes as per your
Thank you for your kind feedback! I will take due note of the comments
in the next documentation patches as well.
I have made all the changes as per your feedback and also corrected
paragraph reflow.
The third version of the patch is attached for your consideration.
--
Oleg Sibiryakov
On
this time.
--
Regards,
Oleg Sibiryakov
Technical Writer
Postgres Professional, The Russian Postgres Company
https://postgrespro.ru
On 13.09.2024 13:50, Oleg Sibiryakov wrote:
Here is a patch without the builtin/built-in corrections (find attached).
But I still believe the issue should be discussed
REL_12_STABLE only)
[1]: https://www.unicode.org/reports/tr29/#Word_Boundaries
[2]:
https://www.postgresql.org/message-id/CAEwbS1R8pwhRkwRo3XsPt24ErBNtFWuReAZhVPJwA3oqo148tA%40mail.gmail.com
Oleg Tselebrovskiy, Postgres Professionaldiff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index
Alexander Korotkov wrote at 2025-07-28 17:23:
On Mon, Jul 28, 2025 at 1:20 PM Alexander Korotkov
wrote:
On 25 Sep 2024, at 18:13, Oleg Tselebrovskiy
wrote:
Greetings, everyone!
One of our clients has found a difference in behaviour of initcap
function when
using different locale
eeded. Still on the
fence
about which patch is better, though
Thoughts?
[1]: https://www.unicode.org/reports/tr29/#Word_Boundaries
Regards, Oleg Tselebrovskiydiff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 74a16af04ad..8a44e0ae593 100644
--- a/doc/src/sgml/func.sgml
+++ b/do
Jeff Davis wrote at 2025-08-05 03:59:
One more thing: we should also change it to "... to upper case (or
title case) and the rest to lower case...". Title case is for scripts
that have characters like 'Dž' (U+01C5).
Done based upon second version of previous patch. Again, there are two
versions
31 matches
Mail list logo
