agora inbox for pgsql-docs@postgresql.org
help / color / mirror / Atom feedFrom: Vik Fearing <vik.fearing@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: nawaz@fast.au.fujitsu.com
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: typo
Date: Mon, 26 Nov 2018 15:29:25 +0100
Message-ID: <fc5b5ce2-720b-7f74-5fa1-1d802784cce5@2ndquadrant.com> (raw)
In-Reply-To: <3912.1543241658@sss.pgh.pa.us>
References: <154319327168.1315.1846953598601966513@wrigleys.postgresql.org>
<20181126065643.GK1776@paquier.xyz>
<CABUevEwvG6FEHhCnY1SNJmaYQDnqTnsSUx0SSWa--KDYYGsO6g@mail.gmail.com>
<14d25c7a-2b03-d98e-5853-0a52ba64ad92@2ndquadrant.com>
<20181126074238.GL1776@paquier.xyz>
<3912.1543241658@sss.pgh.pa.us>
On 26/11/2018 15:14, Tom Lane wrote:
> Michael Paquier <michael@paquier.xyz> writes:
>> On Mon, Nov 26, 2018 at 08:17:06AM +0100, Vik Fearing wrote:
>>> On 26/11/2018 08:03, Magnus Hagander wrote:
>>>> Are you sure that's right? To me the original wording of that sentence
>>>> seems to convey the message properly, and the update done does not?
>
>>> Yeah, I just found this on the committers list and I disagree with the
>>> change as well.
>
>> [... checking around ...]
>> Hm. I have read the sentence and the surroundings a couple of times
>> before doing anything, and using an adverb looked clearer than the
>> adjective. Is an adjective more appropriate than an adverb here because
>> it insists more on the fact that each row is involved? Just trying to
>> grab the difference.
>
> I think that text is mine originally, and it was not a typo. The meaning
> of "table rows proper", in this case, is basically "table rows themelves".
> The first dictionary I looked at gives this example:
>
> PROPER
> Adjective [ chiefly British ]
> ... [ postpositive ] Strictly so called; in its true form.
> "some of the dos and don'ts in espionage proper"
>
> But I can see that a lot of people might not be familiar with that usage,
> so I've got no objections to rewriting it more clearly --- any
> suggestions?
How about
A table that has columns with potentially large entries will have an
associated TOAST table, which is used for out-of-line storage of field
- values that are too large to keep in the table rows proper.
+ values that are too large to keep in the main table storage.
--
Vik Fearing +33 6 46 75 15 36
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
view thread (43+ messages) latest in thread
Message-ID: <fc5b5ce2-720b-7f74-5fa1-1d802784cce5@2ndquadrant.com>
Permalink: ../fc5b5ce2-720b-7f74-5fa1-1d802784cce5@2ndquadrant.com/
Also on: postgresql.org/message-id/fc5b5ce2-720b-7f74-5fa1-1d802784cce5@2ndquadrant.com
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: vik.fearing@2ndquadrant.com, tgl@sss.pgh.pa.us, michael@paquier.xyz, magnus@hagander.net, nawaz@fast.au.fujitsu.com, pgsql-docs@lists.postgresql.org
Subject: Re: typo
In-Reply-To: <fc5b5ce2-720b-7f74-5fa1-1d802784cce5@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox