On Fri, Feb 14, 2020 at 6:09 PM Tom Lane wrote:
> > Language updates attached...mostly kept Tom's suggestions.
>
> Typo (optoin), otherwise LGTM.
Great. Pushed with that tweak.
--
Peter Geoghegan
"Jonathan S. Katz" writes:
> On 2/14/20 8:56 PM, Peter Geoghegan wrote:
>> But everything else looks good, right?
>> I would like to commit this patch shortly.
> Language updates attached...mostly kept Tom's suggestions.
Typo (optoin), otherwise LGTM.
regards, tom lane
On 2/14/20 8:56 PM, Peter Geoghegan wrote:
> On Fri, Feb 14, 2020 at 5:51 PM Tom Lane wrote:
>> Hm, I wouldn't go into that much detail; it'd likely soon be out of
>> date anyway. I had in mind something more like "If the STYLE=website
>> option is used, the generated HTML files will include refe
On Fri, Feb 14, 2020 at 5:51 PM Tom Lane wrote:
> Hm, I wouldn't go into that much detail; it'd likely soon be out of
> date anyway. I had in mind something more like "If the STYLE=website
> option is used, the generated HTML files will include references to
> stylesheets hosted at www.postgresql
"Jonathan S. Katz" writes:
> A potential solution is that we drop the use of "monospace" in relying
> on the OS default and just pick a font. I would say that this is outside
> the scope of the patch that's being proposed, but certainly something to
> look into on the pgweb side given we're creati
On 2/14/20 6:06 PM, Tom Lane wrote:
> "Jonathan S. Katz" writes:
>> To load the webfont, the "main.css" file uses a CSS "@import"
>> instruction, which has a limitation that it can only be used as the top
>> of the file. As main.css is not the first file in the "docs.csS"
>> sandwich, it does not
On 2/12/20 8:15 AM, Jonathan S. Katz wrote:
> On 2/11/20 10:56 PM, Jonathan S. Katz wrote:
>> On 2/11/20 3:49 PM, Jonathan S. Katz wrote:
>>> On 2/11/20 3:41 PM, Peter Geoghegan wrote:
On Tue, Feb 11, 2020 at 11:40 AM Jonathan S. Katz
wrote:
> Anyway, attached is a first attempt at
Alvaro Herrera writes:
> On 2020-Feb-13, Alexander Lakhin wrote:
>> Third (minor) issue is with translation - when I will see some break in
>> the English source, e.g. "split_part('abc~@~def&zwsp;~@~ghi', '~@~',
>> 2)", should I leave the break in the same place, or it's better to move
>> it becau
Hello Alvaro,
14.02.2020 23:16, Alvaro Herrera wrote:
> On 2020-Feb-13, Alexander Lakhin wrote:
>
>> Yes, I was starting with manual &zwsp; insertions into the translation,
>> but later I reduced such insertions just to several dozens. (For
>> example, we still have "3.1415926535&zwsp;8979323846" i
On 2020-Feb-13, Alexander Lakhin wrote:
> Yes, I was starting with manual &zwsp; insertions into the translation,
> but later I reduced such insertions just to several dozens. (For
> example, we still have "3.1415926535&zwsp;8979323846" in the translation.)
> The main issue of the manual approach
On 2020-Feb-14, Jürgen Purtz wrote:
> The attached patch extends the previous one by one more figure, a rework of
> the old explanations plus additional explanations.
So now we have two glossaries being proposed [1] [2], and they don't
have much in common with each other. What to do now? If we
On 2020-Feb-14, Dave Cramer wrote:
> The wiki seems to be the dumping ground for everything that doesn't fit
> into the documentation.
> The problem with this is that if you don't know it is documented there it
> is very difficult to find.
Would it help to have some sort of index? The simplest I
On Fri, 14 Feb 2020 at 11:26, Tom Lane wrote:
> Dave Cramer writes:
> > We have a section in the main docs for conformance
> > https://www.postgresql.org/docs/12/features.html
> > And then this
> https://wiki.postgresql.org/wiki/PostgreSQL_vs_SQL_Standard for
> > divergence.
> > I'd like to see
PG Doc comments form writes:
> In section "11.8 Partial Indexes" it states the following:
> "Matching takes place at query planning time, not at run time. As a result,
> parameterized query clauses do not work with a partial index. For example a
> prepared query with a parameter might specify “x
Dave Cramer writes:
> We have a section in the main docs for conformance
> https://www.postgresql.org/docs/12/features.html
> And then this https://wiki.postgresql.org/wiki/PostgreSQL_vs_SQL_Standard for
> divergence.
> I'd like to see the divergence section put into the main docs so that it is
>
We have a section in the main docs for conformance
https://www.postgresql.org/docs/12/features.html
And then this https://wiki.postgresql.org/wiki/PostgreSQL_vs_SQL_Standard for
divergence.
I'd like to see the divergence section put into the main docs so that it is
easier to find.
Thoughts ?
Da
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/12/indexes-partial.html
Description:
In section "11.8 Partial Indexes" it states the following:
"Matching takes place at query planning time, not at run time. As a result,
parameterized quer
17 matches
Mail list logo
