12.02.2020 23:58, Tom Lane wrote:
> Alexander Lakhin writes:
>> Please look at a less invasive approach that we use at Postgres Pro for
>> some time (mainly for improving the translated documentation, but it
>> works for the original one too). The idea is to add zero-width spaces
>> after/before
Alvaro Herrera writes:
> On 2020-Feb-12, Tom Lane wrote:
>> I also attached a screenshot of a segment of Table 9-31, to show
>> what that layout proposal looks like. It's a little busier, but
>> it does have the advantage that it's clearer how to apply that
>> format to operator tables. The
On 2020-Feb-12, Tom Lane wrote:
> For amusement's sake, attached is a screenshot of what Table 9-33
> looks like in A4 format, with my one-row-per-example patch of
> yesterday plus a few manually-added zero-width spaces to break up
> the examples. This is the first PDF rendering of that table
Adrian Klaver writes:
> On 2/11/20 11:31 PM, Andrus wrote:
>> Also I dont understand why GRANTED BY clauses appear in file. This looks
>> like noice.
>> GRANT documentation
>> https://www.postgresql.org/docs/current/sql-grant.html
>> does not contain GRANTED BY clause. It looks like pg_dumpall
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 a patch. I tried a few different
variations
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/12/populate.html
Description:
I think this could be clearer. In particular, performance of COPY vs INSERT
from a query (INSERT INTO ... SELECT FROM ...) or INSERT with a list of rows
(INSERT
