From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: Kasahara Tatsuhito <kasahara.tatsuhito@gmail.com>
To: Shinya Okano <btokanosn@oss.nttdata.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Add a description to the documentation that toast_tuple_target affects "Main"
Date: Wed, 14 Oct 2020 01:30:06 +0900
Message-ID: <a4941ace-b898-3bd4-270f-2ccc1dc2af07@oss.nttdata.com> (raw)
In-Reply-To: <CAP0=ZVJ9Wh2RnphL4nB6PuhODCxeMBBkzg3=5oSu+1FMOaNK6Q@mail.gmail.com>
References: <93f46e311a67422e89e770d236059817@oss.nttdata.com>
<CAP0=ZVJ9Wh2RnphL4nB6PuhODCxeMBBkzg3=5oSu+1FMOaNK6Q@mail.gmail.com>
On 2020/10/13 10:40, Kasahara Tatsuhito wrote:
> Hi,
>
> On Fri, Oct 9, 2020 at 5:44 PM Shinya Okano <btokanosn@oss.nttdata.com> wrote:
>>
>> Hi,
>>
>> Regarding the toast_tuple_target parameter of CREATE TABLE, the
>> documentation says that it only affects External or Extended, but it
>> actually affects the compression of Main as well.
>>
>> The attached patch modifies the document to match the actual behavior.
> +1
+1
+ we try to compress long column values or to move into TOAST tables, and
"we try to compress and/or move long column values into TOAST tables, and" is better?
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
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-hackers@postgresql.org
Cc: masao.fujii@oss.nttdata.com, kasahara.tatsuhito@gmail.com, btokanosn@oss.nttdata.com
Subject: Re: Add a description to the documentation that toast_tuple_target affects "Main"
In-Reply-To: <a4941ace-b898-3bd4-270f-2ccc1dc2af07@oss.nttdata.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox