| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Replication slots and footguns |
| Date: | 2014-03-14 00:01:26 |
| Message-ID: | CA+TgmoYkHys0Afc_jJ2G4unz0i14rH-xkCdRONc3Afgc1Fr3Xw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Mar 13, 2014 at 6:45 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> On 03/13/2014 01:17 PM, Robert Haas wrote:
>> I think "in use" is just as clear as active, and I think the text
>> Andres proposed previously reads a whole lot more nicely than this:
>>
>> replication slot "%s" is in use by another backend
>
> Then we should change the column name in the pg_stat_replication_slots
> view to "in_use". My point is that the error message and the diagnostic
> view should use the same word, or we're needlessly confusing our users.
I see. That's an interesting point....
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2014-03-14 00:09:25 | Re: Replication slots and footguns |
| Previous Message | Josh Berkus | 2014-03-13 22:45:52 | Re: Replication slots and footguns |