Re: vacuum_truncate configuration parameter and isset_offset - Mailing list pgsql-hackers

From Robert Haas
Subject Re: vacuum_truncate configuration parameter and isset_offset
Date
Msg-id CA+TgmoZpn+TBg5=Cm8R0x-6qfK6+DbvA2eMdZG4ZQTjmaGVpYg@mail.gmail.com
Whole thread Raw
In response to Re: vacuum_truncate configuration parameter and isset_offset  (Nikolay Shaplov <dhyan@nataraj.su>)
Responses Re: vacuum_truncate configuration parameter and isset_offset
List pgsql-hackers
On Wed, Mar 26, 2025 at 2:34 PM Nikolay Shaplov <dhyan@nataraj.su> wrote:
> В письме от среда, 26 марта 2025 г. 21:16:20 MSK пользователь Robert Haas
> написал:
> > The reason why I felt that way is
> > because you were using what seemed to me to be very strong language
> > over what seemed to me to be a very minor issue.
>
> Being not native speaker has it's own difficulties. Plus possible cultural
> differences and so on. I feel emotions about "my precious thing have been
> broken for no reason at all", and this should affect the text, and I guess I
> can not properly keep proper emotional degree as I do not feel fine meaning of
> the words. Yes, I feel emotions, No, I am not yelling,  and certainly I am not
> yelling as final argument.

OK, fair enough.

> Can you please skip the form, that may be not perfect, and see the content. I
> hope that I managed to express the core idea quite clear.

Honestly, I'm still pretty baffled. I understand that different people
may have different stylistic preferences here, and that is fair
enough, but I personally think what Nathan did is more elegant than
inventing an enum type with three possible values. Even if a majority
of people feel otherwise, why is it worth arguing about? I cannot see
how this really makes any great difference.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Nikolay Shaplov
Date:
Subject: Re: vacuum_truncate configuration parameter and isset_offset
Next
From: Kirill Reshke
Date:
Subject: Re: in BeginCopyTo make materialized view using COPY TO instead of COPY (query).