Re: pgsql: Track last_inactive_time in pg_replication_slots.

Поиск
Список
Период
Сортировка
От Bharath Rupireddy
Тема Re: pgsql: Track last_inactive_time in pg_replication_slots.
Дата
Msg-id CALj2ACWDDDpzVzrLoYK-xSQfN64Rs5TtEcGRmTp6qkeX74r6aA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: pgsql: Track last_inactive_time in pg_replication_slots.  (Nathan Bossart <nathandbossart@gmail.com>)
Ответы Re: pgsql: Track last_inactive_time in pg_replication_slots.  (shveta malik <shveta.malik@gmail.com>)
Список pgsql-hackers
On Tue, Mar 26, 2024 at 1:30 AM Nathan Bossart <nathandbossart@gmail.com> wrote:
>
> On Mon, Mar 25, 2024 at 04:49:12PM +0000, Bertrand Drouvot wrote:
> > On Mon, Mar 25, 2024 at 12:25:37PM -0400, Robert Haas wrote:
> >> In the same vein, I think deactivated_at or inactive_since might be
> >> good names to consider. I think they get at the same thing as
> >> released_time, but they avoid introducing a completely new word
> >> (release, as opposed to active/inactive).
> >
> > Yeah, I'd vote for inactive_since then.
>
> Having only skimmed some of the related discussions, I'm inclined to agree
> that inactive_since provides the clearest description for the column.

I think we all have some agreement on inactive_since. So, I'm
attaching the patch for that change.

--
Bharath Rupireddy
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

Вложения

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

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: Large block sizes support in Linux
Следующее
От: Thomas Munro
Дата:
Сообщение: Re: Large block sizes support in Linux