Re: [PATCH] Logical decoding of TRUNCATE

Поиск
Список
Период
Сортировка
От Simon Riggs
Тема Re: [PATCH] Logical decoding of TRUNCATE
Дата
Msg-id CANP8+jJvZs7USgmbE=8amo4UoP28-MHAq5L-R5StG8DFuF-oRQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [PATCH] Logical decoding of TRUNCATE  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Список pgsql-hackers
On 2 April 2018 at 19:30, Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:

>>> ***************
>>> *** 111,116 **** CREATE PUBLICATION <replaceable class="parameter">name</replaceable>
>>> --- 111,121 ----
>>>             and so the default value for this option is
>>>             <literal>'insert, update, delete'</literal>.
>>>            </para>
>>> +          <para>
>>> +            <command>TRUNCATE</command> is treated as a form of
>>> +            <command>DELETE</command> for the purpose of deciding whether
>>> +            to publish, or not.
>>> +          </para>
>>>           </listitem>
>>>          </varlistentry>
>>>         </variablelist>
>>
>> Why is this a good idea?
>
> I think it seemed like a good idea at the time, so to speak, but several
> people have argued against it, so we should probably change this in the
> final version.

Who has argued against it?

I see that Andres has asked twice about it and been answered twice,
but expressed no opinion.
Petr has said he thinks that's right.
Nobody else has commented.

-- 
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: disable SSL compression?
Следующее
От: Andres Freund
Дата:
Сообщение: Re: [PATCH] Logical decoding of TRUNCATE