| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, shveta malik <shveta(dot)malik(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Amit Kapila <akapila(at)postgresql(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Track last_inactive_time in pg_replication_slots. |
| Date: | 2024-03-25 20:00:26 |
| Message-ID: | 20240325200026.GA2924132@nathanxps13 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
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.
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2024-03-25 20:20:42 | Re: pgsql: Track last_inactive_time in pg_replication_slots. |
| Previous Message | Peter Eisentraut | 2024-03-25 19:30:28 | Re: pgsql: make dist uses git archive |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2024-03-25 20:05:51 | Re: Popcount optimization using AVX512 |
| Previous Message | Bharath Rupireddy | 2024-03-25 19:58:00 | Re: New Table Access Methods for Multi and Single Inserts |